On Thu, Mar 09, 2017 at 10:44:42AM +0100, Guillaume Wenzek wrote:
> The full version number is "2.12.0.246.ga2ecc84866" but I don't think
> that's an official number, I'm using my company (Google) apt
> repository.
That's built from the commit at a2ecc84866, which is in the "next"
branch (and is
Thanks for looking into it,
The full version number is "2.12.0.246.ga2ecc84866" but I don't think
that's an official number, I'm using my company (Google) apt
repository.
The git package date is 2017/03/03 while previous version was from
2017/02/16, the commit you identified is actually between t
Junio C Hamano writes:
> Guillaume Wenzek writes:
>
>> After updating to git 2.12.0 on Monday I noticed that the "git branch"
>> wasn't behaving as usual.
>
> Are you sure you are trying 2.12? v2.12.0 and before should behave
> the same way and honor --no-abbrev as far as I know.
>
> On the oth
Guillaume Wenzek writes:
> After updating to git 2.12.0 on Monday I noticed that the "git branch"
> wasn't behaving as usual.
Are you sure you are trying 2.12? v2.12.0 and before should behave
the same way and honor --no-abbrev as far as I know.
On the other hand, 'master' has 93e8cd8b ("Merge
Hi,
After updating to git 2.12.0 on Monday I noticed that the "git branch"
wasn't behaving as usual.
As of today `git branch -vv --no-abbrev` outputs short hashes instead
of long one (as requested by --no-abbrev)[1]
git branch -vv --no-abbrev
* (HEAD detached at 2.12.1)1c69
5 matches
Mail list logo
