From: Linus Torvalds <torvalds@linux-foundation.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what to call it after 2.6.23 but before 2.6.24-rc1?
Date: Sat, 20 Oct 2007 17:37:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0710201732300.10525@woody.linux-foundation.org> (raw)
In-Reply-To: <200710202305.l9KN5R0i008618@agora.fsl.cs.sunysb.edu>
On Sat, 20 Oct 2007, Erez Zadok wrote:
>
> 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?
Sounds like you don't have the tags. Do
git fetch --tags <repo>
to get them.
There can be several reasons why you don't have the tags, but the two most
likely ones are:
- really old versions of git didn't fetch tags by default.
(not very likely, because it's *really* old, but still, worth
mentioning as one possible reason)
- if you don't fetch into a "tracking" branch, but instead do an
"anonymous" fetch into FETCH_HEAD that is then directly merged (or you
just rebase your work on top of it), git won't fetch tags, since it
assumes that you only want to fetch the one head you mentioned.
but regardless, you can always fetch the tags manually.
Linus
prev parent reply other threads:[~2007-10-21 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 21:54 Erez Zadok
2007-10-20 22:26 ` Linus Torvalds
2007-10-20 23:05 ` Erez Zadok
2007-10-21 0:37 ` Linus Torvalds [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.999.0710201732300.10525@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ezk@cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®