On 3/1/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote:
> By the way, I am missing one thing: the Id keyword in the file. The
> problem is that when some user is telling me: there is a bug in the
> function a() that is inside the file b.c, then I can ask him to give me
> the $Id$ tag of the file and I will have the full information about the
> file version.
The problem is: Git does not track files, but rather trees. So, there is
no sane way to add an Id.
But all is not lost! If your colleague sends you the offending file, you
can calculate the object name from it by
$ git-hash-object -t blob <filename>
Wont work. The ids in question are really strings embedded into object.
Something like:
$Id 1.2 user filename.c$
They can be found, extracted from the binary and sent to developer
with a bug report. It's more of a build signature.
IOW, the colleague in question has to have the source, which,
I suspect, he wont.
Of course, it's very simple to embed the HEAD into build and
tell the tester to send the SHA-1 in case of bug report.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html