Re: moving Hive to git

Reg. disabling merge commits, if Apache is ok installing git server-side hook scripts, setting up a pre-receive hook could be a possible option: http://stackoverflow.com/questions/2039773/have-remote-git-repository-refuse-merge-commits-on-push On Wed, Sep 17, 2014 at 10:56 AM, Sergey Shelukhin

Re: moving Hive to git

d to write bash scripts to replace one git command (e.g. git clean), and branching is difficult. On Wed, Sep 17, 2014 at 9:31 AM, E.L. Leverenz wrote: > This is the rest of the message I meant to send on the "moving Hive to > git" thread, but then did an accidental send. Apache r

Re: moving Hive to git

I can check how HBase operates without merge commits... cherry-picking seems tedious, at least without the script - too easy to forget, and that would arguably be more harmful than a stray merge commit. On Wed, Sep 17, 2014 at 10:47 AM, Brock Noland wrote: > Hi, > > I am generally +1 on the prop

Re: moving Hive to git

Hi, I am generally +1 on the proposal. I'd strongly want to disable merge commits. They are far too easy to accidently push. If there is no option to disable them, one option would be to do what we did in flume. Basically: 1) Trunk operates as normal. 2) We always have the next release branch op

Re: moving Hive to git

Can we look at how this is done in Hbase or Hadoop. If these projects migrated on git then I am sure that they might have faced similar issues. On 17 Sep 2014 22:37, "E.L. Leverenz" wrote: > This is the rest of the message I meant to send on the "moving Hive to > git&quo

moving Hive to git

This is the rest of the message I meant to send on the "moving Hive to git" thread, but then did an accidental send. Apache rejected several attempts as spam, so I'm sending this from a different email account. This list summarizes the previous discussion, with my que

Re: moving Hive to git

For me, the advantages of git are: 1. Each user's working copy contains the global history of the project. So while I'm disconnected in an airplane; I can look at history and logs, switch between branches, and do merges. 2. It makes it very easy to work on development branches and rebase off of tru

Re: moving Hive to git

I'm not convinced git would be better. Could someone please spell out the advantages? In particular: 1. "... git is more powerful and easy to use (once you go past the learning curve!)" -- Lefty On Tue, Sep 16, 2014 at 4:27 PM, Sergey Shelukhin wrote: > It seems there was consensus t

Re: moving Hive to git

It seems there was consensus that we should move. Any volunteers to do it? I can try to find the details on how HBase migrated. On Fri, Sep 12, 2014 at 7:10 PM, Lefty Leverenz wrote: > We had a related discussion March 5 - 10: llsmugcwkuryr5tb > th

Re: moving Hive to git

We had a related discussion March 5 - 10: llsmugcwkuryr5tb through rq66qe2cpfgw7o5s . -- Lefty On Fri, Sep 12, 2014 at 9:33 PM, Sergey Shelukhin wrote: > Hi. > Many Apache projects are moving to git f

moving Hive to git

Hi. Many Apache projects are moving to git from svn; HBase moved recently, and as far as I have heard Hadoop has moved too. Are there any objections to moving Hive to use git too? I wanted to start a preliminary discussion. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of