All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Add --pretty=changelog
Date: Fri, 02 Mar 2007 11:15:03 +0100	[thread overview]
Message-ID: <87abywrly0.fsf@latte.josefsson.org> (raw)
In-Reply-To: <7vejo8ezde.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri\, 02 Mar 2007 02\:03\:25 -0800")

Junio C Hamano <junkio@cox.net> writes:

> 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.

Yes, actually, that seems like a better solution.

Btw, there is a custom to work around cvs translating empty log
messages into '*** empty log message ***' strings, and that is to
commit a log consisting of '.'.  Translating both of those cvs log
messages into a '' git log message, during cvs-import, seems like a
useful change.

>> 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.

Sorry for the trouble!

Also thanks, Johannes, for working so quickly on this.  Seeing the
first version of the ChangeLog output from your patched git allowed me
to realize that the imported cvs history seemed ok.  After replacing
'cvs2cl' and 'cvsco' I couldn't find any other more cvs-specific
features in the project.  I have just released the first version of
libtasn1 from git instead of cvs.  More projects will follow...

/Simon

  reply	other threads:[~2007-03-02 10:15 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
2007-03-02 10:15           ` Simon Josefsson [this message]
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=87abywrly0.fsf@latte.josefsson.org \
    --to=simon@josefsson.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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.