Re: Funny 'git describe --contains' output

2012-08-29 Thread Greg KH
On Tue, Aug 28, 2012 at 11:36:46PM -0700, Junio C Hamano wrote: > Junio C Hamano writes: > > > Greg KH writes: > > > >> In the Linux kernel tree, commit 0136db586c028f71e7cc21cc183064ff0d5919 > >> is a bit "odd". > >> > >> If I go to look to see what release it was in, I normally do: > >>$ g

Re: Funny 'git describe --contains' output

2012-08-28 Thread Junio C Hamano
Junio C Hamano writes: > Greg KH writes: > >> In the Linux kernel tree, commit 0136db586c028f71e7cc21cc183064ff0d5919 >> is a bit "odd". >> >> If I go to look to see what release it was in, I normally do: >> $ git describe --contains 0136db586c028f71e7cc21cc183064ff0d5919 >> v3.6-rc1~5

Re: Funny 'git describe --contains' output

2012-08-28 Thread Junio C Hamano
Greg KH writes: > In the Linux kernel tree, commit 0136db586c028f71e7cc21cc183064ff0d5919 > is a bit "odd". > > If I go to look to see what release it was in, I normally do: > $ git describe --contains 0136db586c028f71e7cc21cc183064ff0d5919 > v3.6-rc1~59^2~56^2~76 > ... > Any ideas?

Funny 'git describe --contains' output

2012-08-28 Thread Greg KH
Hi, In the Linux kernel tree, commit 0136db586c028f71e7cc21cc183064ff0d5919 is a bit "odd". If I go to look to see what release it was in, I normally do: $ git describe --contains 0136db586c028f71e7cc21cc183064ff0d5919 v3.6-rc1~59^2~56^2~76 However, it really showed up first in t