From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Simon Josefsson <simon@josefsson.org>, git@vger.kernel.org
Subject: Re: Replacement for cvs2cl, for generating ChangeLog
Date: Tue, 27 Feb 2007 11:27:25 -0800 [thread overview]
Message-ID: <7v8xejflk2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0702271336050.22628@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Tue, 27 Feb 2007 13:37:23 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Tue, 27 Feb 2007, Simon Josefsson wrote:
>
>> * Is there a tool that produce ChangeLog files in the GNU format,
>> based on the git logs? Similar to the 'cvs2cl' tool. The output
>> should look like:
>> ...
> Let me hack something.
I do not know why you want to pile something like this into
builtin-log. It would add maintenance burden and I do not see a
gain from it.
One beauty of git is being scriptable. When somebody new asks
for something like this, I think it is much more productive to
demonstrate the power of scriptability than piling random crap
in the core.
next prev parent reply other threads:[~2007-02-27 19:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 11:41 Replacement for cvs2cl, for generating ChangeLog Simon Josefsson
2007-02-27 12:23 ` Junio C Hamano
2007-02-27 12:37 ` Johannes Schindelin
2007-02-27 14:40 ` Sergey Vlasov
2007-02-28 14:08 ` gitco - replacement for cvsco Simon Josefsson
2007-02-28 19:55 ` Yann Dirson
2007-02-28 21:31 ` Simon Josefsson
2007-02-27 15:19 ` Replacement for cvs2cl, for generating ChangeLog Johannes Schindelin
2007-02-28 14:12 ` Simon Josefsson
2007-02-27 19:27 ` Junio C Hamano [this message]
2007-02-27 19:45 ` Johannes Schindelin
2007-02-27 20:54 ` Johannes Schindelin
2007-02-27 12:57 ` Andy Parkins
2007-02-27 15:56 ` Johannes Schindelin
2007-02-27 21:27 ` Robin Rosenberg
2007-02-27 21:50 ` Junio C Hamano
2007-02-27 22:22 ` Johannes Schindelin
2007-02-27 22:12 ` Johannes Schindelin
2007-02-28 14:27 ` Simon Josefsson
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=7v8xejflk2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=simon@josefsson.org \
/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).