Re: RFS: git2cl
Hi Antonio,
Sorry for delay.
Please help me to understand the issue a bit better:
The number of spaces between Name and Email - is it significant?
As far as I can see GNU documents do not say if there should be one or two
spaces. (However in their example I see two spaces)
Is this important for you?
To summarize your experience:
git2cl:
* put one space between Name and Email
('git log --pretty' command put two spaces)
* show list of changed files
('git log pretty' don't)
Regards,
Dmitry.
On Saturday 26 November 2011 20:37:35 Antonio Ospite wrote:
> On Sat, 26 Nov 2011 16:30:31 +1100
>
> Dmitry Smirnov <onlyjob@member.fsf.org> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Dear Mentors,
> >
> > I'm looking for sponsor for my package git2cl
> >
> > Package name : git2cl
> > URL : http://josefsson.org/git2cl/
> > License : GPL-2+
> > Section : utils
> >
> > It is a simple tool to convert git logs to GNU ChangeLog format
> > according to format specification:
> > http://www.gnu.org/prep/standards/html_node/Change-Logs.html
>
> Just a comment about the problem git2cl solves, sorry for going a bit
> Off Topic, in my projects I use this command to generate a GNU Style
> ChangeLog:
>
> git log --pretty="format:%ad %aN <%aE>%n%n%x09* %s%d%n" --date=short
>
> or a variant which prints the timezone too in the date field:
>
> git log --pretty="format:%ai %aN <%aE>%n%n%x09* %s%d%n"
>
> Notable differences with git2cl:
> * Puts _two_spaces_ between author's name and author's email, like
> the document you quote shows. git2cl does not do that.
> * Does not show the list of changed files, which is not a problem
> _for_me_ since I usually put a context hint before the commit
> message anyways, like:
> subsystem: actual commit message...
>
> Regards,
> Antonio
>
> > Package available for review from:
> >
> >
> > http://mentors.debian.net/debian/pool/main/g/git2cl/git2cl_2.0+git2008082
> > 71242-1.dsc
> >
> > Packaging is rather trivial so it likely to be easy to review.
> >
> > Regards,
> > Dmitry.
Reply to: