I'd suggest looking into git-subtree as well, if we wanted to maintain a single-development-tree experience. Submodules have a reputation (well-deserved, IMHO) of being somewhat unwieldy to work with; using git-subtree to manage linked trees can be a bit more automation/setup work, but can also provide a much smoother user experience.
On Mon, May 12, 2014 at 8:03 PM, Matt Sicker <boa...@gmail.com> wrote: > Something I've been experimenting with is using git submodules. You > basically have a repository for each "submodule", then you can have another > repository that groups them all together for convenience. It's handy for > making a sort of stable master that points to the latest tag or something > similar. It's kind of confusing, but I think it works well for when people > want to check out a project corresponding to the latest stable rather than > the trunk (which would normally be stable anyway). > > > On 12 May 2014 21:19, Antoine Levy Lambert <anto...@gmx.de> wrote: > > > > > Hi, > > > > resending a message which I sent on May 7th but might have been lost > > completely due to our infrastructure problems last week : > > > > > > > > > > > To actually migrate to git, we could either make one INFRA JIRA for all > > the ant family of projects, or do this one step at a time. > > > > > > Concerning the antlibs, I suppose we want one git module for each > antlib > > - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a > > common folder which ought to be on its own. > > > > > > If we do it one step at a time we could start with ant proper, then > move > > to ivy, ivyde, easyant and the antlibs. > > > > > > What do you think ? > > > > > > Antoine > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > > For additional commands, e-mail: dev-h...@ant.apache.org > > > > > > > -- > Matt Sicker <boa...@gmail.com> >
