GIT and CVS
Jan Kratochvil
jan.kratochvil@redhat.com
Thu Oct 13 22:45:00 GMT 2011
On Fri, 14 Oct 2011 00:19:17 +0200, Alfred M. Szmidt wrote:
> While useful, they don't replace information of this type:
>
> * configure.ac (tic6x-*-*): Remove gdb from noconfigdirs.
git log -p:
tic6x-*-*)
- noconfigdirs="$noconfigdirs gdb sim"
+ noconfigdirs="$noconfigdirs sim"
git annotate:
005efcbe (Joseph Myers 2010-03-23 16:05:34 +0000 1022) tic6x-*-*)
34dd72a9 ( qiyao 2011-08-14 12:28:15 +0000 1023) noconfigdirs="$noconfigdirs sim"
005efcbe (Joseph Myers 2010-03-23 16:05:34 +0000 1024) ;;
->
git show 34dd72a9
What's wrong with it? And if I search which commit changed it:
git log -p -Sgdb configure.ac
> You still have to store that information _somewhere_, be it in a file
> or in the commit message.
Still there should be stored + shown the associated mail which completely
misses here and which is stored there by GIT.
Currently I have to always look up the associated mails with each CVS commit
to have the reasons and background of each patch; it is really a lose of
engineering time looking up all the mails by hand I have to do with CVS:
http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-upstream.patch;hb=f16
->
...
FYI: implement new DWARF macro proposal
http://sourceware.org/ml/gdb-patches/2011-07/msg00732.html
http://sourceware.org/ml/gdb-cvs/2011-07/msg00212.html
...
[patch][python] Fix sigsegv when a printer fails to return a value and string_print is set.
http://sourceware.org/ml/gdb-patches/2011-07/msg00719.html
http://sourceware.org/ml/gdb-cvs/2011-07/msg00234.html
...
etc.
> I just don't see how annotate/log replaces
> that here, maybe it should? I don't know, but entries like that are
> super useful to trace history of things.
When I was a newbie to GDB I would not see the reason why string "gdb" was
removed from variable "noconfigdirs". I would like to find out the mail
submit/reasoning/approval. I tried now but I failed to find the mail.
Contrary to it you can see the explanation of a commit in:
http://git.kernel.org/?p=git/git.git;a=commit;h=d4e85a1afe0a3310a3c8336c2824775901cc27d7
It is true I would prefer URL / Message-ID for the mail thread, it is not
commonly there even with GIT. There are some other patch management software
for such tracking.
Regards,
Jan
More information about the Gdb
mailing list