From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: [PATCH] New script: git-changelog.perl
Date: Fri, 2 Nov 2007 20:18:02 +0100 [thread overview]
Message-ID: <200711022018.02926.jnareb@gmail.com> (raw)
Subject: Re: [PATCH] New script: git-changelog.perl
From: "Ronald Landheer-Cieslak" <ronald@landheer-cieslak•com>
To: "Jakub Narebski" <jnareb@gmail•com>
On Nov 2, 2007 1:07 PM, Jakub Narebski <jnareb@gmail•com> wrote:
> [Cc: Ronald Landheer-Cieslak <ronald@landheer-cieslak•com>,
> git@vger•kernel.org]
>
> Ronald Landheer-Cieslak wrote:
>
>> I've written a little script that will format the changes as reported
>> by git-log in a ChangeLog-like format. Entries look like this:
>> <date>\t<author>\n\t<sha1>: <subject>
>
> How it compares to existing git2cl tool?:
> http://josefsson.org/git2cl/
> http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
I must admit I didn't know about git2cl. The first difference I see is
that it's simpler and has less dependencies: my script doesn't use any
external modules (e.g. it doesn't parse the date) but just parses a
formatted output from git-log.
Other than that, there's not much difference: my output is a bit
sparser and my script invokes the proper git-log command by itself, so
you don't have to pipe through it (i.e. all you do is git-changelog >
ChangeLog to get your change log) but that's pretty much it.
If you want, you can have a look at it at
git://vlinder.landheer-cieslak.com/git/git.git#topic/git-log-changelog
rlc
--
Ronald Landheer-Cieslak
Software Architect
http://www.landheer-cieslak.com/
New White Paper: "Three Good Reasons to Plan Ahead"
next reply other threads:[~2007-11-02 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 19:18 Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 15:55 [PATCH] New script: git-changelog.perl Ronald Landheer-Cieslak
2007-11-02 17:07 ` Jakub Narebski
2007-11-02 18:27 ` Johannes Schindelin
2007-11-02 18:53 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711022018.02926.jnareb@gmail.com \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox