I'm all for clarity.  Git makes me nervous, but I'm sure I'll get used to
it with a little help from my friends.

The wiki would need to be updated by someone who knows more about git than
I do.  Ignoring some contributor meeting minutes, "svn" occurs in 14 Hive
wiki pages
<https://cwiki.apache.org/confluence/dosearchsite.action?queryString=svn&where=Hive&type=page&startIndex=0>.
Make that 13 because we can ignore PhabricatorCodeReview
<https://cwiki.apache.org/confluence/display/Hive/PhabricatorCodeReview>.

-- Lefty

On Wed, Apr 15, 2015 at 7:59 PM, Thejas Nair <thejas.n...@gmail.com> wrote:

> We need to be clear on how the process works with move to git, I am
> not familiar with the process followed by other groups that use git
> currently.
>
> A [DISCUSS] thread for discussing the specifics might be appropriate.
> I assume the central git repository would still be the one in apache.
> Does that we mean we work using *github* pull requests like what spark
> does ? -
> https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-ContributingCode
>
> I haven't done this, but I assume it is possible to pull a github pull
> request into the apache git. Would that be the way to merge the patch
> in ?
> One (misplaced?) concern I have about git, is that merging pull
> requests would result in lots of branches and it would be hard to
> understand the sequence of changes. (maybe rebasing the changes in
> pull request before commit would help).
>
> I would like to see more clarity on this before we move ahead.
>
>
> On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <ser...@apache.org>
> wrote:
> > Hi.
> > We’ve been discussing this some time ago; this time I¹d like to start an
> > official vote about moving Hive project to git from svn.
> >
> > I volunteer to facilitate the move; that seems to be just filing INFRA
> > jira, and following instructions such as verifying that the new repo is
> > sane.
> >
> > Please vote:
> > +1 move to git
> > 0 don’t care
> > -1 stay on svn
> >
> > +1.
> >
> >
> >
>

Reply via email to