Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of lhofhansl@yahoo.com designates
 98.139.213.126 as permitted sender)
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>
Message-ID: <1400886991.74251.YahooMailNeo@web140606.mail.bf1.yahoo.com>
Date: Fri, 23 May 2014 16:16:31 -0700 (PDT)
From: lars hofhansl <larsh@apache.org>
Reply-To: lars hofhansl <larsh@apache.org>
Subject: Re: We have our first victim
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
In-Reply-To: 
 <CAMUu0w81bGj_3BU27KMb2b1FAe1G-mBqKYez7ASHh6XFYZC1qg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="1905101558-1414819059-1400886991=:74251"

--1905101558-1414819059-1400886991=:74251
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

It would have prevented me from fixing the history, though, after I messed =
it up simply by forgetting to rebase before a push.=0AI do think that anybo=
dy who does a force push needs to explain him/herself, though.=0A=0A=0A-- L=
ars=0A=0A=0A=0A________________________________=0A From: Enis S=C3=B6ztutar=
 <enis.soz@gmail.com>=0ATo: "dev@hbase.apache.org" <dev@hbase.apache.org> =
=0ASent: Friday, May 23, 2014 4:13 PM=0ASubject: Re: We have our first vict=
im=0A =0A=0AForce push should be disabled by default for all branches I thi=
nk.=0A=0AEnis=0A=0A=0A=0AOn Fri, May 23, 2014 at 3:35 PM, Andrew Purtell <a=
purtell@apache.org> wrote:=0A=0A> Makes sense, earlier Jake was talking abo=
ut how 'trunk' is a "protected=0A> branch".=0A>=0A>=0A> On Fri, May 23, 201=
4 at 3:22 PM, Konstantin Boudnik <cos@apache.org>=0A> wrote:=0A>=0A> > I th=
ink INFRA only disables force-pushes to the master: the rest of the=0A> > b=
ranches is a fair game ;)=0A> >=0A> > Cos=0A> >=0A> > On Fri, May 23, 2014 =
at 03:12PM, lars hofhansl wrote:=0A> > > I just had to fix up the history o=
n the 0.94 branch, because I forgot=0A> to=0A> > > rebase after a pull (and=
 I had some committed changes already).=0A> > >=0A> > > git will happily le=
t you push stuff, even if that messes up the history=0A> > (and=0A> > > reo=
rder commits, in my case my local change was ordered before the=0A> pulled=
=0A> > > changes).=0A> > > It's not wrong, since I should have rebased my c=
hanges. Just... uhm...=0A> > surprising :)=0A> > >=0A> > >=0A> > > Scary, b=
ut it worked and at least git gives me enough tools to fix=0A> > things.=0A=
> > >=0A> > > -- Lars=0A> > >=0A> > >=0A> > >=0A> > > _____________________=
___________=0A> > >=C2=A0 From: Andrew Purtell <apurtell@apache.org>=0A> > =
> To: "dev@hbase.apache.org" <dev@hbase.apache.org>=0A> > > Sent: Friday, M=
ay 23, 2014 10:22 AM=0A> > > Subject: We have our first victim=0A> > >=0A> =
> >=0A> > > Ram pushed up a commit as a new branch 'trunk' instead of to 'm=
aster'.=0A> I=0A> > > will file an infra ticket to nuke the new branch 'tru=
nk' as this is=0A> going=0A> > > to confuse people. Objections?=0A> > >=0A>=
 > > --=0A> > > Best regards,=0A> > >=0A> > > =E2=95=90=C2=A0 - Andy=0A> > =
>=0A> > > Problems worthy of attack prove their worth by hitting back. - Pi=
et=0A> Hein=0A> > > (via Tom White)=0A> >=0A>=0A>=0A>=0A> --=0A> Best regar=
ds,=0A>=0A>=C2=A0 =C2=A0 - Andy=0A>=0A> Problems worthy of attack prove the=
ir worth by hitting back. - Piet Hein=0A> (via Tom White)=0A>
--1905101558-1414819059-1400886991=:74251--