Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # dev - DISCUSSION: Move to GIT?


Copy link to this message
-
Re: DISCUSSION: Move to GIT?
Sergey Shelukhin 2013-10-25, 18:30
+1, also only use svn to commit
On Fri, Oct 25, 2013 at 11:10 AM, Enis Söztutar <[EMAIL PROTECTED]> wrote:

> +1000.
>
> Enis
>
>
> On Fri, Oct 25, 2013 at 10:58 AM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:
>
> > +1.  I've actually only used SVN to commit patches.
> >
> > I'd suggest we maintain the same commit style (straight line rebased
> > commits per release branch, branches off trunk for major features) after
> > the move to git as opposed to the github style (lots of branch/merges).
> >
> > Jon.
> >
> >
> > On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <[EMAIL PROTECTED]>
> wrote:
> >
> > > +1 I've actually been using git to do most of my work lately.
> > >
> > >
> > > On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <[EMAIL PROTECTED]> wrote:
> > >
> > > > git is more powerful and flexible.
> > > >
> > > > 2013/10/26 Ted Yu <[EMAIL PROTECTED]>:
> > > > > +1 too.
> > > > >
> > > > >
> > > > > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <
> > [EMAIL PROTECTED]
> > > > >wrote:
> > > > >
> > > > >> +1
> > > > >>
> > > > >> Do all my work in git anyways :)
> > > > >>
> > > > >> On Friday, October 25, 2013, Stack wrote:
> > > > >>
> > > > >> > At yesterday's dev meetup -- minutes to follow -- it was
> suggested
> > > we
> > > > >> move
> > > > >> > the project to git as our repo of truth.
> > > > >> >
> > > > >> > What do folks think?  How patches are contributed and committer
> > will
> > > > have
> > > > >> > to change to match git-flow.
> > > > >> >
> > > > >> > Josh Eiser, an accumulo committer, was at the dev meetup
> yesterday
> > > and
> > > > >> was
> > > > >> > kind enough to write up the steps involved moving their project
> > > over.
> > > > >>  See
> > > > >> > the discussion on how they come up w/ a process in particular.
> > > > >> >
> > > > >> > St.Ack
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > ---------- Forwarded message ----------
> > > > >> > From: Josh Elser <[EMAIL PROTECTED] <javascript:;>>
> > > > >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > > > >> > Subject: Accumulo's transition to git
> > > > >> > To: Stack <[EMAIL PROTECTED] <javascript:;>>
> > > > >> >
> > > > >> >
> > > > >> > Stack,
> > > > >> >
> > > > >> > As promised, here's the info that I had collected when Accumulo
> > made
> > > > the
> > > > >> > transition from SVN to Git.
> > > > >> >
> > > > >> > Make sure you have some mailing list consensus, and then open up
> > an
> > > > INFRA
> > > > >> > ticket. For us, we requested the following things
> > > > >> >
> > > > >> > 1. Specify which SVN branches you want in Git, and if you want
> > them
> > > > >> > renamed. Also, which you want the default Git branch to be on
> > clone.
> > > > >> >
> > > > >> > 2. If you have any contribs, specify which other SVN path you
> want
> > > as
> > > > >> their
> > > > >> > own Git repos.
> > > > >> >
> > > > >> > 3. Specify the format of the subject for the git commit
> > > notifications
> > > > >> email
> > > > >> > and to which mailing list.
> > > > >> >
> > > > >> > 4. Request update of mirroring on git.a.o and
> github.com/apache/.
> > ..
> > > > >> >
> > > > >> > 5. Transition from svn2jira to git2jira (honestly, I don't
> > remember
> > > > what
> > > > >> > this was anymore.. maybe commenting on Jira for issue mentions
> in
> > > > >> commits)
> > > > >> >
> > > > >> > 6. Request delivery of pull-requests to a given mailing list.
> > > > >> >
> > > > >> > 7. Request update reviewboard to the new repo.
> > > > >> >
> > > > >> > Our INFRA ticket can be found at [1]
> > > > >> >
> > > > >> > FWIW, we also had a huge discussion about how we were going to
> use
> > > > Git so
> > > > >> > that we didn't constantly duplicate a bunch of commits
> > > cherry-picking
> > > > >> > changes everywhere. There was a bunch of teaching we had to do
> to
> > > make
> > > > >> sure
> > > > >> > we had a good commit history and could still use features like
> > > > >> git-bisect.
> > > > >> > The result of that is at [2].
> > > > >> >
> > > > >> > Joe Stein also sent us Kafka's use of Git that was helpful when

CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.