Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-14 Thread Andrew Eikum
On Fri, Feb 14, 2014 at 01:08:32PM -0800, Junio C Hamano wrote: > Andrew Eikum writes: > > > My worry is having "2." hang around for another decade or longer. I'd > > rather see X.0.0 denote a major feature release (currently represented > > as 1.X.0), with X.Y.0 for minor enhancements and X.Y.Z

Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-14 Thread Junio C Hamano
Andrew Eikum writes: > My worry is having "2." hang around for another decade or longer. I'd > rather see X.0.0 denote a major feature release (currently represented > as 1.X.0), with X.Y.0 for minor enhancements and X.Y.Z for bugfix. We need three categories: (1) potentially incompatible, (2) f

Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-14 Thread Andrew Eikum
On Fri, Feb 14, 2014 at 12:10:05PM -0800, Junio C Hamano wrote: > Andrew Eikum writes: > > > On Wed, Feb 12, 2014 at 01:59:41PM -0800, Junio C Hamano wrote: > >> As a workaround to make life easier for third-party tools, the > >> upcoming major release will be called "Git 1.9.0" (not "Git 1.9").

Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-14 Thread Junio C Hamano
Andrew Eikum writes: > On Wed, Feb 12, 2014 at 01:59:41PM -0800, Junio C Hamano wrote: >> As a workaround to make life easier for third-party tools, the >> upcoming major release will be called "Git 1.9.0" (not "Git 1.9"). >> The first maintenance release for it will be "Git 1.9.1", and the >> ma

Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-14 Thread Andrew Eikum
On Wed, Feb 12, 2014 at 01:59:41PM -0800, Junio C Hamano wrote: > As a workaround to make life easier for third-party tools, the > upcoming major release will be called "Git 1.9.0" (not "Git 1.9"). > The first maintenance release for it will be "Git 1.9.1", and the > major release after "Git 1.9.0"

Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-14 Thread Junio C Hamano
"brian m. carlson" writes: >> Changes to some scripted Porcelains use unsafe variable >> substitutions and still need to be tightened. >> >> Will merge to 'next'. > > Junio, did you want a reroll with that fixed commit message, or will you > fix it up yourself? I haven't merged them yet---if

Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-14 Thread brian m. carlson
On Wed, Feb 12, 2014 at 01:59:41PM -0800, Junio C Hamano wrote: > * bc/gpg-sign-everywhere (2014-02-11) 9 commits > - pull: add the --gpg-sign option. > - rebase: add the --gpg-sign option > - rebase: parse options in stuck-long mode > - rebase: don't try to match -M option > - rebase: remove

What's cooking in git.git (Feb 2014, #04; Wed, 12)

2014-02-12 Thread Junio C Hamano
Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. As a workaround to make life easier for third-party tools, the upcoming major release will be called "Git 1.9.0" (not "Git 1.9"). The first main