[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] conversion from cvs repository to git
From: |
Werner LEMBERG |
Subject: |
Re: [ft-devel] conversion from cvs repository to git |
Date: |
Thu, 01 Jan 2009 20:46:16 +0100 (CET) |
> >This is not sufficient IMHO, if someone really wants to fix this. For
> >example, a line like
> >
> > * builds/modules.ml (CLOSE_MODULE, REMOVE_MODULE), builds/detect.mk
> >
> >(from 2008-02-11) says nothing; the most important information has
> >been truncated.
>
> Umm, "git log" command shows untruncated log for the entry,
> also gitk displays untruncated comment in the pane for
> comments (I attached screenshot). However, we see truncated
> comment in the top pane showing revision tree, and "Parent"
> and "Child" in the pane for comments. I think, the truncation
> of the comment is not by git itself but by the user interface
> of the git repository browsers, like gitk
Correct. However, the web interface also shows just a single line of
the commit entry, so it's essential IMHO to produce a `header line'
for commits.
> In the case of 2008-02-11 changeset, joining 4 lines comment to
> single line can avoid the comment truncation problem, but such long
> comment would not fit to most interfaces of git repository browsers.
> I guess, the expected work would be writing new short comment up to
> 40 characters or so.
Say, 60 characters.
> Werner, my understanding is correct?
Exactly. It's basically an easy job but quite time consuming.
Werner