All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: git-gui problem with version number.
Date: Fri, 27 Jul 2007 01:36:27 -0400	[thread overview]
Message-ID: <20070727053627.GI20052@spearce.org> (raw)
In-Reply-To: <85y7h25sg6.fsf@lola.goethe.zz>

David Kastrup <dak@gnu.org> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> 
> > David Kastrup <dak@gnu.org> wrote:
> >> Hi, git-gui does not get along with the creativeness in git
> >> versioning:
> >
> > What version of git-gui?  gitgui-0.7.5-67-g91464df and later have
> > fixes to handle all of the fun cases in git versioning.  Like the
> > one you have here.
> >  
> >> git-gui
> >> Error in startup script: expected version number but got "1.5.3.rc2.4.g726f9-dirty"
> >>     while executing
> >> "package vcompare $_git_version $vr"
> 
> The one coming with the mentioned version number.  I suspect that this
> may be a matter of the Perl libraries being used: I experience this on
> an Ubuntu Dapper, but not on other (newer) systems compiled from the
> same source.

Ah.  Junio hasn't pulled those version numbering fixes from me yet.
Because I haven't asked him to pull in a while.  That explains that.

There's no Perl involved in git-gui, except for the Perl in an
underlying Git command it might invoke.  So perhaps you were
talking about Tcl above?

Anyway, you can setup a build with the most recent 'stable
development' version of git-gui:

  git checkout -b with-new-gitgui
  git pull -s subtree git://repo.or.cz/git-gui.git

That's really all Junio does.  Although I think he does actually try
to test it briefly before pushing a final release out to the public.
Just to make sure Git hasn't broken anything really obvious in
git-gui.  ;-)

-- 
Shawn.

  reply	other threads:[~2007-07-27  5:36 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 [this message]
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
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=20070727053627.GI20052@spearce.org \
    --to=spearce@spearce.org \
    --cc=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 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.