git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-gui problem with version number.

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jul 29, 2007, 07:10 UTC
Message-ID
<20070729071030.GL20052@spearce.org>
In-Reply-To
<86lkd2mcsu.fsf@lola.quinscape.zz>
David Kastrup <dak@gnu.org> wrote:
Show 12 quoted lines
> 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.

Did you not see me already state in this thread that its already been fixed? Latest git-gui already has the problem dealt with, and that latest version will be included in git 1.5.3 when it ships.

Nevertheless, thanks for the problem report.
-- 
Shawn.
Previous: David KastrupNext: David Kastrup
Message 10 of 11 in “git-gui problem with version number.”
  1. David KastrupJul 26, 2007
  2. Shawn O. PearceJul 27, 2007
  3. David KastrupJul 27, 2007
  4. Shawn O. PearceJul 27, 2007
  5. David KastrupJul 27, 2007
  6. Shawn O. PearceJul 27, 2007
  7. David KastrupJul 27, 2007
  8. David KastrupJul 27, 2007
  9. David KastrupJul 27, 2007
  10. Shawn O. PearceJul 29, 2007
  11. David KastrupJul 29, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.