Hello,

2015-01-06 18:55 GMT+01:00 sebb <seb...@gmail.com>:

> On 6 January 2015 at 17:24, Benedikt Ritter <brit...@apache.org> wrote:
> > Hello Sebb,
> >
> > 2015-01-06 18:01 GMT+01:00 sebb <seb...@gmail.com>:
> >
> >> -1
> >>
> >> When the first components moved to Git, the agreement was that these
> >> would be used to iron out any problems and create some documentation
> >> to enable developers who know SVN to migrate to Git.
> >>
> >
> > The procedure I'm following here has been discussed already [1].
>
> That was after the original discussions.
>
> >
> >>
> >> AFAICT there is no such documentation.
> >>
> >> It does not have to be extensive, just some details of commonly used
> >> SVN commands and their Git equivalents.
> >>
> >> For example:
> >>
> >> svn co, ci, status, diff, revert
> >> How to create a tag
> >>
> >
> > I'm not going to create such a "how to use git" documentation. I think
> > everyone of us is capable of using google, stackoverflow and man pages.
> > What you're looking for may be [2].
> >
>
> Thanks, that's useful.
>
> >>
> >> Also what changes are needed to the pom.
> >>
> >
> > The only thing that has to be changed is the scm information (Luc,
> correct
> > me, if I'm wrong here).
>
> Yes, but a worked example would help.
> Git seems to have lots of different URLs for the same thing.
>
> >
> >>
> >> This would probably be best done as a Wiki page, at least initially.
> >>
> >
> > I think it is sufficient to update our release guide [3,4] to contain the
> > equivalent git commands.
>
> That needs to be done, yes, but I was referring to developer use of
> Git; creating and applying patches etc.
>
> > Since I'm the only one who has released [lang] for
> > a year now and the [math] people already know how to do it, I don't see
> > this as super critical. Or are you planning to RM for [lang] any time
> soon?
>
> No, I was not planning to RM Lang.
>
> However I would like to be able to commit fixes etc without having to
> spend a lot of time learning new commands.
>
> > Would you be willing to withdraw your -1 if the release guide is updated?
>
> Yes, of course.
>

Sorry that this took forever, I've been busy at work. But today I finally
got some time to write something together [1]. There are still two open
issues (retrieving all commits since the last release and git + maven
release plugin). I'd like to ask the guys from [math] to add/correct
anything missing/wrong.

Is this enough for you to withdraw your proposal so that I can announce
this lazy vote as passed?

TIA!
Benedikt

[1] http://svn.apache.org/r1663139


>
> > Regards,
> > Benedikt
> >
> > [1] http://markmail.org/message/gtbdy4ozqcogerfi
> > [2] http://git.or.cz/course/svn.html
> > [3] http://commons.apache.org/releases/prepare.html
> > [4] http://commons.apache.org/releases/release.html
> >
> >
> >>
> >>
> >>
> >> On 3 January 2015 at 12:28, Benedikt Ritter <brit...@apache.org> wrote:
> >> > Hi all,
> >> >
> >> > since we made first (good?) experiences with Commons Math using git as
> >> > primary VCS, I'd like to call a vote to migrate Commons Lang to git.
> >> >
> >> > This vote by lazy consensus will close no sooner than 72 hours from
> now,
> >> > i.e. after 2014/01/06 13:30 CET.
> >> >
> >> > Thanks,
> >> > Benedikt
> >> >
> >> > --
> >> > http://people.apache.org/~britter/
> >> > http://www.systemoutprintln.de/
> >> > http://twitter.com/BenediktRitter
> >> > http://github.com/britter
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
> >
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Reply via email to