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
brian m. carlson sand...@crustytoothpaste.net 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
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 will
Andrew Eikum aei...@codeweavers.com 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
On Fri, Feb 14, 2014 at 12:10:05PM -0800, Junio C Hamano wrote:
Andrew Eikum aei...@codeweavers.com 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
Andrew Eikum aei...@codeweavers.com 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
On Fri, Feb 14, 2014 at 01:08:32PM -0800, Junio C Hamano wrote:
Andrew Eikum aei...@codeweavers.com 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
7 matches
Mail list logo
