From: David Chanters <david.chanters@googlemail.com>
To: "Marcus D. Hanwell" <marcus.hanwell@kitware.com>
Cc: Chris Packham <judge.packham@gmail.com>, git@vger.kernel.org
Subject: Re: Generating GNU-style Changelog from git commits
Date: Sun, 17 Apr 2011 16:14:35 +0100 [thread overview]
Message-ID: <BANLkTi=bGnT6n9WqGz309ZPgzL9KRAkMzQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikQvOkoFSXXC3oUKQfASo8==qdgxA@mail.gmail.com>
On 17 April 2011 02:47, Marcus D. Hanwell <marcus.hanwell@kitware.com> wrote:
> https://github.com/cryos/avogadro/blob/master/scripts/gitlog2changelog.py
>
> If there are better ways of doing this I would certainly be
> interested, but have not spent much time on this since writing the
> initial script. We had a similar desire, but didn't want to end up
> resolving conflicts around a file in version control.
Thanks, all. I shall look into it. :)
David
prev parent reply other threads:[~2011-04-17 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 22:46 Generating GNU-style Changelog from git commits David Chanters
2011-04-17 0:53 ` Chris Packham
2011-04-17 1:47 ` Marcus D. Hanwell
2011-04-17 15:14 ` David Chanters [this message]
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='BANLkTi=bGnT6n9WqGz309ZPgzL9KRAkMzQ@mail.gmail.com' \
--to=david.chanters@googlemail.com \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.com \
--cc=marcus.hanwell@kitware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).