Your message dated Mon, 22 Feb 2010 19:31:26 -0600
with message-id <[email protected]>
and subject line Re: Please expose GIT_REPO_VERSION
has caused the Debian Bug report #486403,
regarding Please expose GIT_REPO_VERSION
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
486403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486403
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-core
Version: 1:1.5.5.4-1
Severity: wishlist
Tags: patch
Hi,
Please find the patch below (I believe it won't break any porcelain
above it)
which exposes the value of GIR_REPO_VERSION (git's internal repository
format) via --version. It will benefit the recently added to the
dpkg-source "3.0 (git)" source format. If it changes in some incompatible way
in the future it would be possible to identify which source package used the
old format if that information is recorded in a header field in the .dsc
file. Rf: #457345.
--- help.c.orig 2008-06-15 23:42:39.000000000 +0300
+++ help.c 2008-06-15 23:44:06.000000000 +0300
@@ -504,7 +504,7 @@
int cmd_version(int argc, const char **argv, const char *prefix)
{
- printf("git version %s\n", git_version_string);
+ printf("git version %s (repo version %d)\n", git_version_string,
GIT_REPO_VERSION);
return 0;
}
--
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB
--- End Message ---
--- Begin Message ---
George Danchev wrote:
> Jonathan Nieder writes:
>> You see, git’s repository format _has_ changed in incompatible ways a
>> few times already without any corrusponding bump in the repository
>> format version. Examples: the addition of packed refs, and the
>> addition of alternative packed object formats. Maybe that is
>> unfortunate, but it has not caused any major breakage I know of. Part
>> of the problem is perhaps that different features are added at the
>> same time and it is not immediately obvious which one deserves the
>> higher repository version number.
>
> Well, if that is the case, I'd agree we can close that bug. Agreed?
Okay.
Thanks anyway for the idea --- thoughts on making git easier to use by
humans and scripts will still be needed for a while yet.
Maybe some day there will be something analogous to a soname for git
repository formats, and then we can revisit this.
Kind regards,
Jonathan
--- End Message ---
