[Bug 1370] New: org.openmoko.dev git commitlog . . . difficult to read/skim
bugzilla-daemon at bugzilla.openmoko.org
bugzilla-daemon at bugzilla.openmoko.org
Fri Apr 25 23:32:22 CEST 2008
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1370
Summary: org.openmoko.dev git commitlog . . . difficult to
read/skim
Product: Site Infrastructure
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Lists
AssignedTo: gismo at openmoko.org
ReportedBy: cwixon at usa.net
CC: buglog at lists.openmoko.org
This may be a matter of personal preference, but I found it far easier to browse
the openmoko svn commitlog when the patched file was listed in the subject line
rather than the new git revision number, which is basically human-unreadable.
So, to give some examples, this is good:
25 Apr 15:47 thomas r4398 - in trunk/src/target/opkg: libopkg tests
. . . because I can see who made the commit, what package was affected, and
there's a human-readable sequence number.
And this is not too helpful:
25 Apr 08:36 oe org.openmoko.dev: f29e2561976b51ce011555b5e1c6812affdb781e
. . . because all messages come from "oe" and say nothing about what was
patched. So I have to open and read all of them to see if there's anything that
is affecting what I am working on.
Also in the git commitlog, at the end of the message, the patch is presented
without (apparent) newlines, so it's one giant blob of text.
I don't know how configurable this is, but I think there's room for improvement
if it can be done.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the buglog
mailing list