From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Re: git-gui problem with version number.
Date: Fri, 27 Jul 2007 11:11:13 +0200 [thread overview]
Message-ID: <86lkd2mcsu.fsf@lola.quinscape.zz> (raw)
In-Reply-To: 86k5smnvhw.fsf@lola.quinscape.zz
David Kastrup <dak@gnu.org> writes:
> Now that is funny. I am pretty sure (or rather _have_ been pretty
> sure) that I cloned the respective repositories with the same command.
> Yet now both are up-to-date according to git-pull (and have identical
> .config contents), and the first compiles version git version
> 1.5.3.rc2.41.gb47b1 while the second compiles version
> 1.5.3.rc3.7.gd58e-dirty. Both have been cloned from git.git, the
A combination of rebasing and pushing made the difference go away and
made git-gui work again. Nevertheless, it would be a good idea not to
balk at the dirty version strings.
--
David Kastrup
next prev parent reply other threads:[~2007-07-27 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 11:20 git-gui problem with version number David Kastrup
2007-07-27 4:46 ` Shawn O. Pearce
2007-07-27 5:25 ` David Kastrup
2007-07-27 5:36 ` Shawn O. Pearce
2007-07-27 5:43 ` David Kastrup
2007-07-27 5:48 ` Shawn O. Pearce
2007-07-27 5:50 ` David Kastrup
2007-07-27 7:42 ` David Kastrup
2007-07-27 9:11 ` David Kastrup [this message]
2007-07-29 7:10 ` Shawn O. Pearce
2007-07-29 9:08 ` David Kastrup
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=86lkd2mcsu.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).