From: Junio C Hamano <junkio@cox.net>
To: Simon Josefsson <simon@josefsson.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Add --pretty=changelog
Date: Fri, 02 Mar 2007 02:03:25 -0800 [thread overview]
Message-ID: <7vejo8ezde.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <87hct4roqa.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 02 Mar 2007 10:14:53 +0100")
Simon Josefsson <simon@josefsson.org> writes:
> The problem here is that CVS insert '*** empty log message ***' when
> you didn't supply a log message, and doing something intelligent with
> such logs would be useful.
If that is indeed the case then I suspect that cvs-to-git
conversion should know about it and strip the artificial
string.
In any case, as I already said a few times in this thread, I
think what you did is the right approach --- to read from "git
log --numstat" output and format the output to match the precise
detail of your project's liking with an external script.
> But I want more than the oneline comment in the ChangeLog? There is
> no size limit on ChangeLog messages, and having as much information as
> possible available is better.
I think this was purely underspecification when your request was
passed to Johannes.
I've merged Johannes's gnucl series to 'next' but haven't pushed
out, so I'll revert it.
next prev parent reply other threads:[~2007-03-02 10:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.63.0702271621120.22628@wbgn013.biozentrum.uni-wuerz burg.de>
2007-02-27 15:21 ` [PATCH] Add --pretty=changelog Johannes Schindelin
2007-02-27 15:38 ` Nicolas Pitre
2007-02-27 15:57 ` Johannes Schindelin
2007-02-27 23:11 ` Eric Wong
2007-02-27 23:22 ` Junio C Hamano
2007-02-28 1:58 ` [PATCH 4/3] Rename --pretty=changelog to --pretty=gnucl, and fix a bug Johannes Schindelin
2007-02-28 2:52 ` Nicolas Pitre
2007-02-28 12:44 ` [PATCH] --amend Rename --pretty=changelog to --pretty=gnucl Johannes Schindelin
2007-03-02 8:49 ` Junio C Hamano
2007-03-02 14:28 ` [PATCH] print_wrapped_text: fix output for negative indent Johannes Schindelin
2007-03-02 14:29 ` [PATCH] --pretty=gnucl: avoid line wrapping before the comma Johannes Schindelin
2007-03-03 12:38 ` [PATCH] --amend Rename --pretty=changelog to --pretty=gnucl Junio C Hamano
2007-03-03 14:13 ` Johannes Schindelin
2007-03-03 20:07 ` Junio C Hamano
2007-03-01 15:23 ` [PATCH] Add --pretty=changelog Simon Josefsson
2007-03-01 18:15 ` Johannes Schindelin
2007-03-01 18:27 ` Shawn O. Pearce
2007-03-01 18:40 ` Johannes Schindelin
2007-03-02 4:39 ` Junio C Hamano
2007-03-02 9:14 ` Simon Josefsson
2007-03-02 10:03 ` Junio C Hamano [this message]
2007-03-02 10:15 ` Simon Josefsson
2007-03-02 14:09 ` Johannes Schindelin
2007-03-03 14:12 ` 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=7vejo8ezde.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.