Dan is also forgetting Pro Git [1]. It's an excellent resource, and
if you haven't looked at it, please do.
[1]
Software Engineer
Open Source Advocate
PGP key id: 926CCFF5
PGP key available at:
On Sat, Oct 16, 2010 at 14:33, Dan Allen <dan.j.allen(a)gmail.com> wrote:
For those of you who aren't familiar with git, now's the time
to learn.
Fortunately, there are a tremendous number of resources.
I would start by just looking through the help pages at
github.com, since
those instructions are going to be geared towards the environment in which
we'll be working:
http://help.github.com/
Steve also wrote a post recently with lots of Git tips and tricks. Check it
out!
http://in.relation.to/Bloggers/HibernateMovesToGitGitTipsAndTricks
Finally, if you have any questions, just swing by #seam-dev and you'll
likely find someone there to give you some pointers (or we'll figure it out
together).
-Dan
On Sat, Oct 16, 2010 at 3:40 PM, Jason Porter <lightguard.jp(a)gmail.com>
wrote:
>
> Migration to git is complete, you can find the modules at the urls
> listed below (in the first email of this thread). Please be sure to
> create your own fork for each module you work on.
>
> Jason Porter
>
http://lightguard-jp.blogspot.com
>
http://twitter.com/lightguardjp
>
> Software Engineer
> Open Source Advocate
>
> PGP key id: 926CCFF5
> PGP key available at:
keyserver.net,
pgp.mit.edu
>
>
>
> On Sat, Oct 16, 2010 at 12:02, Dan Allen <dan.j.allen(a)gmail.com> wrote:
> > Migration is underway. All repositories listed below should be
> > considered
> > frozen indefinitely. We'll send a mail when the git repositories are
> > ready.
> > -Dan
> >
> > On Fri, Oct 15, 2010 at 6:18 PM, Dan Allen <dan.j.allen(a)gmail.com>
> > wrote:
> >>
> >> We plan to migrate the Seam 3 source code from SVN to git this weekend
> >> (Saturday). Each SVN root will be migrated to it's matching git
> >> repository
> >> in the seam organization at
github.com. All the history, including
> >> tags,
> >> will be preserved.
> >> Below is the mapping of what will be migrated (I've used the public
> >> urls
> >> just as a point of reference). Note that the xml repository is changing
> >> to
> >> xml-config and the remoting to js-remoting.
> >>
http://anonsvn.jboss.org/repos/seam/modules/documents ->
> >>
http://github.com/seam/documents
> >>
http://anonsvn.jboss.org/repos/seam/modules/drools ->
> >>
http://github.com/seam/drools
> >>
http://anonsvn.jboss.org/repos/seam/modules/faces ->
> >>
http://github.com/seam/faces
> >>
http://anonsvn.jboss.org/repos/seam/modules/international ->
> >>
http://github.com/seam/international
> >>
http://anonsvn.jboss.org/repos/seam/modules/jbpm ->
> >>
http://github.com/seam/jbpm
> >>
http://anonsvn.jboss.org/repos/seam/modules/jms ->
> >>
http://github.com/seam/jms
> >>
http://anonsvn.jboss.org/repos/seam/modules/persistence ->
> >>
http://github.com/seam/persistence
> >>
http://anonsvn.jboss.org/repos/seam/modules/remoting ->
> >>
http://github.com/seam/js-remoting
> >>
http://anonsvn.jboss.org/repos/seam/modules/resteasy ->
> >>
http://github.com/seam/resteasy
> >>
http://anonsvn.jboss.org/repos/seam/modules/security ->
> >>
http://github.com/seam/security
> >>
http://anonsvn.jboss.org/repos/seam/modules/servlet ->
> >>
http://github.com/seam/servlet
> >>
http://anonsvn.jboss.org/repos/seam/modules/wicket ->
> >>
http://github.com/seam/wicket
> >>
http://anonsvn.jboss.org/repos/seam/modules/xml ->
> >>
http://github.com/seam/xml-config
> >>
http://anonsvn.jboss.org/repos/seam/sandbox/modules/scheduling ->
> >>
http://github.com/seam/scheduling
> >>
http://anonsvn.jboss.org/repos/seam/build ->
> >>
http://github.com/seam/build
> >>
http://anonsvn.jboss.org/repos/seam/dist ->
http://github.com/seam/dist
> >>
http://anonsvn.jboss.org/repos/seam/examples ->
> >>
http://github.com/seam/examples
> >> We'll also be importing two existing git repositories:
> >>
http://github.com/codylerum/seam-mail ->
http://github.com/seam/mail
> >>
http://github.com/LightGuard/seam-exception-handling ->
> >>
http://github.com/seam/catch
> >> Jason and I will be in the #seam-dev IRC channel while the migration is
> >> taking place.
> >> We'll be following the same development process as Weld. You fork your
> >> repository and send pull requests based on JIRAs. Pete will handle or
> >> delegate integration of the pull requests. We'll update the module
> >> handbook
> >> to reflect this process.
> >> -Dan
> >> --
> >> Dan Allen
> >> Principal Software Engineer, Red Hat | Author of Seam in Action
> >> Registered Linux User #231597
> >>
> >>
http://mojavelinux.com
> >>
http://mojavelinux.com/seaminaction
> >>
http://www.google.com/profiles/dan.j.allen
> >
> >
> >
> > --
> > Dan Allen
> > Principal Software Engineer, Red Hat | Author of Seam in Action
> > Registered Linux User #231597
> >
> >
http://mojavelinux.com
> >
http://mojavelinux.com/seaminaction
> >
http://www.google.com/profiles/dan.j.allen
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen