Re: what to call it after 2.6.23 but before 2.6.24-rc1?

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Linus Torvalds <torvalds@...>
Cc: Erez Zadok <ezk@...>, <linux-kernel@...>
Date: Saturday, October 20, 2007 - 7:05 pm

In message <alpine.LFD.0.999.0710201517530.10525@woody.linux-foundation.org>, Linus Torvalds writes:

[...]


Bingo.  git-describe is what I was looking for.  It's more accurate to use
as a reference even after rcN come out.  My current cloned tree of yours
sez:

	v2.6.23-6562-g8add244

One more small git question: I keep a separate tree for unionfs, which I
rebase often based on your tree.  But my tree sez:

$ git-describe
v2.6.21-rc1-22880-g3a1848d

"v2.6.21-rc1"?  What am I missing (some tags I forgot to pull?)  Why isn't
git-describe saying that I'm based on your latest tree?

Thanks,
Erez.
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
what to call it after 2.6.23 but before 2.6.24-rc1?, Erez Zadok, (Sat Oct 20, 5:54 pm)
Re: what to call it after 2.6.23 but before 2.6.24-rc1?, Linus Torvalds, (Sat Oct 20, 6:26 pm)
Re: what to call it after 2.6.23 but before 2.6.24-rc1? , Erez Zadok, (Sat Oct 20, 7:05 pm)
Re: what to call it after 2.6.23 but before 2.6.24-rc1? , Linus Torvalds, (Sat Oct 20, 8:37 pm)