Re: Missing some trunk commit history

Friday, December 15, 2017 at 11:06 AM To: Eric Yang <ey...@hortonworks.com> Cc: Chris Douglas <cdoug...@apache.org>, Eric Yang <ey...@apache.org>, Arun Suresh <asur...@apache.org>, Sunil G <sun...@apache.org>, Hadoop Common <common-dev@hadoop.apache.org> Subj

Re: Missing some trunk commit history

> know about the rebase option is turned on by default for > Hadoop. > >> > > > > >> > > > Regards, > >> > > > Eric > >> > >

Re: Missing some trunk commit history

> this way we see it as a single commit ? Although we will >> > loose >> > > the feature >> > > > branch history (I am ok with that though) >> > > > >> > > > Cheers >> > >

Re: Missing some trunk commit history

> > merge - >> > > > this way we see it as a single commit ? Although we will >> > loose >> > > the feature >> > > > branch history (I am ok with that though) >> > > > >> > > &g

Re: Missing some trunk commit history

ic Yang < > > > ey...@hortonworks.com> wrote: > > > > > > > > > Thank you for the pointer. I guess all merge are done > > using > > > rebase + > > > > > mer

Re: Missing some trunk commit history

-Arun > > > > > > > > On Thu, Dec 14, 2017 at 11:32 AM, Eric Yang < > > > ey...@hortonworks.com> wrote: > > > > > > > > > Thank you for the pointer. I guess all merge are done > > using > &g

Re: Missing some trunk commit history

; > Would it be more useful to merge without rebasing for > feature > > branch merge > > > > to avoid timeline confusions? The argument for not > rebasing, > > it would be > > > > easier to find the root cause of trunk failure was

Re: Missing some trunk commit history

r not rebasing, > it would be > > > easier to find the root cause of trunk failure was due to > merge or some > > > recent commits. > > > > > > Regards, > > > Eric > &

Re: Missing some trunk commit history

to > merge or some > > > recent commits. > > > > > > Regards, > > > Eric > > > > > > From: Sunil G <sun...@apache.org> > > > Date: Thursday, December 14, 2017 at 11:11 A

Re: Missing some trunk commit history

> > > From: Sunil G <sun...@apache.org> > > Date: Thursday, December 14, 2017 at 11:11 AM > > To: Eric Yang <ey...@hortonworks.com> > > Cc: Hadoop Common <common-dev@hadoop.apache.org> > > Subject: Re: Missing some tr

Re: Missing some trunk commit history

> > > Regards, > > Eric > > > > From: Sunil G <sun...@apache.org> > > Date: Thursday, December 14, 2017 at 11:11 AM > > To: Eric Yang <ey...@hortonworks.com> > > Cc: Hadoop Common <common-dev@hadoop.apache.

Re: Missing some trunk commit history

17 at 11:11 AM > To: Eric Yang <ey...@hortonworks.com> > Cc: Hadoop Common <common-dev@hadoop.apache.org> > Subject: Re: Missing some trunk commit history > > Hi Eric. > > A branch merge has happened during that time, and hence you might

Re: Missing some trunk commit history

easier to find the root cause of trunk failure was due to merge or some > recent commits. > > Regards, > Eric > > From: Sunil G <sun...@apache.org> > Date: Thursday, December 14, 2017 at 11:11 AM > To: Eric Yang <ey...@hortonworks.com> > Cc: Hadoop Common <comm

Re: Missing some trunk commit history

the root cause of trunk failure was due to merge or some recent commits. Regards, Eric From: Sunil G <sun...@apache.org> Date: Thursday, December 14, 2017 at 11:11 AM To: Eric Yang <ey...@hortonworks.com> Cc: Hadoop Common <common-dev@hadoop.apache.org> Subject: Re: Missing some tr

Re: Missing some trunk commit history

Hi Eric. A branch merge has happened during that time, and hence you might have seen some old commits from that branch. If you go down further, you could see those commits. Copied from my git log: commit 40b0045ebe0752cd3d1d09be00acbabdea983799 Author: Weiwei Yang Date: Wed

Missing some trunk commit history

Hi all, While troubleshooting a trunk build failure, I notice the commit history for trunk between Nov 30th to Dec 6th are squashed or disappeared for no reason. This seems to have taken place in the last 24 hours. I can see the commit logs from github UI. When doing a new clone from Apache