Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com
 designates 209.85.160.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAMUu0w81bGj_3BU27KMb2b1FAe1G-mBqKYez7ASHh6XFYZC1qg@mail.gmail.com>
References: 
 <CA+RK=_De_a+a96e4yC1Fhcu0Zc1V7Fd9o-dSpfC=RmdhGc-7KA@mail.gmail.com>
	<1400883177.21629.YahooMailNeo@web140601.mail.bf1.yahoo.com>
	<20140523222227.GD6333@boudnik.org>
	<CA+RK=_DDfm3sbkmA69eNuRrR=zvfpFTccVhVO_8PRUz1RD-hmg@mail.gmail.com>
	<CAMUu0w81bGj_3BU27KMb2b1FAe1G-mBqKYez7ASHh6XFYZC1qg@mail.gmail.com>
Date: Fri, 23 May 2014 16:38:30 -0700
Message-ID: 
 <CALte62ybsG=+9kKCjpA=EdKmYhw_=jy4-UtCO9z=+OyGF84OPw@mail.gmail.com>
Subject: Re: We have our first victim
From: Ted Yu <yuzhihong@gmail.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=20cf303dd74a26848d04fa19ba49

--20cf303dd74a26848d04fa19ba49
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It is a good idea to disable force push.


On Fri, May 23, 2014 at 4:13 PM, Enis S=C3=B6ztutar <enis.soz@gmail.com> wr=
ote:

> Force push should be disabled by default for all branches I think.
>
> Enis
>
>
> On Fri, May 23, 2014 at 3:35 PM, Andrew Purtell <apurtell@apache.org>
> wrote:
>
> > Makes sense, earlier Jake was talking about how 'trunk' is a "protected
> > branch".
> >
> >
> > On Fri, May 23, 2014 at 3:22 PM, Konstantin Boudnik <cos@apache.org>
> > wrote:
> >
> > > I think INFRA only disables force-pushes to the master: the rest of t=
he
> > > branches is a fair game ;)
> > >
> > > Cos
> > >
> > > On Fri, May 23, 2014 at 03:12PM, lars hofhansl wrote:
> > > > I just had to fix up the history on the 0.94 branch, because I forg=
ot
> > to
> > > > rebase after a pull (and I had some committed changes already).
> > > >
> > > > git will happily let you push stuff, even if that messes up the
> history
> > > (and
> > > > reorder commits, in my case my local change was ordered before the
> > pulled
> > > > changes).
> > > > It's not wrong, since I should have rebased my changes. Just...
> uhm...
> > > surprising :)
> > > >
> > > >
> > > > Scary, but it worked and at least git gives me enough tools to fix
> > > things.
> > > >
> > > > -- Lars
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >  From: Andrew Purtell <apurtell@apache.org>
> > > > To: "dev@hbase.apache.org" <dev@hbase.apache.org>
> > > > Sent: Friday, May 23, 2014 10:22 AM
> > > > Subject: We have our first victim
> > > >
> > > >
> > > > Ram pushed up a commit as a new branch 'trunk' instead of to
> 'master'.
> > I
> > > > will file an infra ticket to nuke the new branch 'trunk' as this is
> > going
> > > > to confuse people. Objections?
> > > >
> > > > --
> > > > Best regards,
> > > >
> > > > =E2=95=90  - Andy
> > > >
> > > > Problems worthy of attack prove their worth by hitting back. - Piet
> > Hein
> > > > (via Tom White)
> > >
> >
> >
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hei=
n
> > (via Tom White)
> >
>

--20cf303dd74a26848d04fa19ba49--