Re: [Plplot-devel] More discussion of our adopted rebase workflow

2014-09-24 Thread Alan W. Irwin
On 2014-09-24 11:00-0700 David MacMahon wrote: > Hi, Alan, > > On Sep 23, 2014, at 10:41 PM, Alan W. Irwin wrote: > >> On 2014-09-23 16:01-0700 David MacMahon wrote: >> >>> Just to nit pick: [...] >> >> Your comment above caught this nit-picker's attention. :-) > > Takes one to know one! :-) :-)

Re: [Plplot-devel] More discussion of our adopted rebase workflow

2014-09-24 Thread David MacMahon
Hi, Alan, On Sep 23, 2014, at 10:41 PM, Alan W. Irwin wrote: > On 2014-09-23 16:01-0700 David MacMahon wrote: > >> Just to nit pick: [...] > > Your comment above caught this nit-picker's attention. :-) Takes one to know one! :-) :-) :-) > What I was referring to (see README.developers) is we

Re: [Plplot-devel] More discussion of our adopted rebase workflow

2014-09-23 Thread Alan W. Irwin
On 2014-09-23 16:01-0700 David MacMahon wrote: > Just to nit pick: isn't this more of a pre-push check rather than client side enforcement? Nit picking aside, I agree that with rebase-only it easier to check for potential push problems on the client side *before* pushing. Hi David: Your comment

Re: [Plplot-devel] More discussion of our adopted rebase workflow

2014-09-23 Thread David MacMahon
Hi, Alan, On Sep 23, 2014, at 12:35 PM, Alan W. Irwin wrote: > On 2014-09-23 09:54-0700 David MacMahon wrote: > >> Emailing patches is tedious and error prone. > > I disagree. I have been applying user-generated patches to PLplot for > years without any patch-related errors. And I really like

[Plplot-devel] More discussion of our adopted rebase workflow

2014-09-23 Thread Alan W. Irwin
Hi David: I changed the subject line to something more appropriate. On 2014-09-23 09:54-0700 David MacMahon wrote: > Hi, Alan, > > On Sep 22, 2014, at 12:37 PM, Alan W. Irwin wrote: > >> You are much more experienced with git than me. However, I thought >> that rebasing a public branch was alwa