All of lore.kernel.org
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Thomas Koeller <thomas@koeller.dyndns.org>
Cc: linux-mips@linux-mips.org
Subject: Re: git problem
Date: Thu, 29 Nov 2007 12:32:38 +0100	[thread overview]
Message-ID: <474EA356.3070303@gmail.com> (raw)
In-Reply-To: <200711281950.46472.thomas@koeller.dyndns.org>

Thomas Koeller wrote:
> on my machine I have clones of both the linux-mips and
> Linus' kernel tree. I recently found that git-describe
> behaves differently in those trees:
 
[snip]

> The commit is of course present in both trees. AFAIK the
> 'cannot describe' error shows if there are no tags at all,
> but this is not the case; .git/refs/tags is fully populated.

Not really, it can happen if the commit you're trying to describe and
all of its parents are not tagged.

> Has anybody got a clue as to what may be wrong here?

Is the commit originally part of Linus' tree and was pulled later by
Ralf ?

If so, it probably means that the commits committed by Ralf in his
tree, which are the tagged ones, have no relationship with the ones
pulled from Linus.

		Franck

  parent reply	other threads:[~2007-11-29 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 18:50 git problem Thomas Koeller
2007-11-28 20:19 ` Ralf Baechle
2007-11-29 11:32 ` Franck Bui-Huu [this message]
2007-11-29 13:09   ` Ralf Baechle
2007-11-29 14:38     ` Franck Bui-Huu
2007-11-29 15:06       ` Ralf Baechle
2007-11-29 22:47   ` Thomas Koeller
  -- strict thread matches above, loose matches on Subject: below --
2008-04-02 19:21 Ken Moffat
2011-10-03  2:57 Larry Finger

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=474EA356.3070303@gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=thomas@koeller.dyndns.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.