ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Boudart <jeanlouis.boud...@gmail.com>
Subject Re: migration to git : next steps
Date Sat, 24 May 2014 10:58:50 GMT
As far as i can tell everything seems ok.

I have checked :
 * ant
 * ivy
 * antunit
 * every easyant-* repo

All branches / tags are there with latest commits.



2014-05-23 19:49 GMT+02:00 antoine@gmx.de <antoine@gmx.de>:

> Jake Farrell has finished the migration, we are asked to verify. Right now
> I am at work so cannot verify but will look during the weekend.
>
> See
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-7759
>
> Antoine Levy-Lambert
>
> ----- Reply message -----
> From: "Antoine Levy Lambert" <antoine@gmx.de>
> To: "Ant Developers List" <dev@ant.apache.org>
> Subject: migration to git : next steps
> Date: Thu, May 22, 2014 10:17 PM
>
> Hi,
>
> moving to actual action.
>
> jfarrell from infra is setting our svn repo
> http://svn.apache.org/repos/asf/ant read-only to prepare for the import.
>
> The ant site will remain in svn and stay RW during the process.
>
> Antoine
>
> On May 20, 2014, at 10:25 PM, Matt Sicker <boards@gmail.com> wrote:
>
> > I'm going to have to look into subtree as I've been using submodule at
> work
> > lately and it's becoming a huge mess.
> >
> >
> > On 20 May 2014 13:39, Charles Duffy <charles@dyfis.net> wrote:
> >
> >> 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 <boards@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 <antoine@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-unsubscribe@ant.apache.org
> >>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Matt Sicker <boards@gmail.com>
> >>>
> >>
> >
> >
> >
> > --
> > Matt Sicker <boards@gmail.com>
>



-- 
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message