Which msysGit version corresponds to which official Git version?

I'm using msysGit. Upon shell startup it says "Welcome to Git (version 1.5.5-preview20080413)". That's the latest msysGit version.

git --version says "git version 1.5.5.1015.g9d258"

I'd like to know which official Git version (as cloned from git://git.kernel.org/pub/scm/git/git.git) corresponds to my msysGit version.

git checkout 9d258 didn't work.

Any hints? Is there a Website or another mailing list for msysGit?

    Dirk

On May 24, 2008, at 2:45 PM, Dirk Süsserott wrote:

It's not in official git.git. msysgit is based on official git 1.5.5, i.e. tag v1.5.5 (9d8318051). msysGit adds, however, a lot of commits that are (not yet) in official git.git.

http://code.google.com/p/msysgit/

	Steffen

Steffen Prohaska schrieb:

Thanks a lot, that's exactly what I was looking for. :-)

BTW, I couldn't checkout the commit '9d8318051' you mentioned from git.git. No such something, it said. When I checked out 'v1.5.5' it said my HEAD is now '1d2375d'. Probably I messed up my clone, but I thought the commit id was unique for all time.

Whoa, stop. I re-cloned git.git to a different directory and succesfully checked out 9d8318051. Look:

$ git clone git://git.kernel.org/pub/scm/git/git.git
  > Initialized empty Git repository in [...]/test/git/.git/
  > remote: Counting objects: 72806, done.?[K
  > remote: Compressing objects: 100% (22377/22377), done.?[K
  > remote: Total 72806 (delta 52252), reused 68863 (delta 49051)?[K
  > Receiving objects: 100% (72806/72806), 15.67 MiB | 202 KiB/s, done.
  > Resolving deltas: 100% (52252/52252), done.

$ cd git

$ git checkout 9d8318051
  > Note: moving to "9d8318051" which isn't a local branch
  > If you want to create a new branch from this checkout, you may do so
  > (now or later) by using -b with the checkout command again. Example:
  >   git checkout -b <new_branch_name>
  > HEAD is now at 1d2375d... GIT 1.5.5

I'd expected that "HEAD is now at 9d8318051...". Wrong?
When I checkout "1d2375d" it says the very same:
  > HEAD is now at 1d2375d... GIT 1.5.5

So what's the difference then between 9d8318051 and 1d2375d? gitk doesn't know about 9d8318051 at all. Seems that there are two ways to get to v1.5.5: via 9d... and via 1d.... Is that right or did I misunderstand sth. here?

    Dirk

Hi,

9d831 is the v1.5.5 tag object; 1d237 is the commit it points to. When you pass a tag reference to checkout, it gets dereferenced to the corresponding commit.

Jan Krueger schrieb:

Ahh, that explains it. :-) Thanks! I sometimes mix up the different IDs Git emitts.

Dirk Süsserott wrote:

9d8318051 is a tag object that creates the v1.5.5 tag:

$ git cat-file -p 9d8318051 object 1d2375ddfee18bd3effd2c1f98527cc2f8b1df0a type commit tag v1.5.5 tagger Junio C Hamano <gitster@pobox.com> Mon Apr 7 21:57:56 2008 -0700

GIT 1.5.5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBH+vtXwMbZpPMRm5oRAlfBAJwPP5W9HvoAHzmD1AoWpRtcyQ/uoACfVkCc M7H1LhvSXz+h2+08bieh3uU= =uTP0 -----END PGP SIGNATURE-----

Hi,

On Sun, 25 May 2008, Dirk Süsserott wrote:

Why did you not just update your tracking (AKA remote) branches with "git fetch"?

Ciao, Dscho

Johannes Schindelin schrieb:

I just wanted to make sure... I'm still practicing, you know. I sometimes use the git.git repo to try out some of the commands I hear about here, because it has a reasonable number of branches and tags. Thought I screwed it up. ;-)

On the other hand, I don't know how I lost tha sha1 9d8318051 (which is the tag's ID, as I've learned). Possibly I didn't actually lose it but wasn't aware of the right commands. git fetch, for an example.