From: Matthias Hopf <mhopf@suse.de>
To: git@vger.kernel.org
Subject: Re: git-rebase nukes multiline comments
Date: Mon, 19 Jun 2006 11:53:00 +0200 [thread overview]
Message-ID: <20060619095300.GB15209@suse.de> (raw)
In-Reply-To: <7vwtbgbsax.fsf@assigned-by-dhcp.cox.net>
On Jun 16, 06 16:21:26 -0700, Junio C Hamano wrote:
> Having said that, I would say it is a bug. We should be able to
> rebase, cherry-pick and/or rebase a patch with an arbitrary
> binary garbage in the commit log message (I think the latter two
> command do). But because of the reason (2) above, it is very
> low on my priority to change it.
I understand. Many thanks for your explainations. I think this intended
log format should be documented somewhere, that would help a lot. I
don't think that many developers using git in CVS style know about this
convention.
Said that, I assume git nuking the multiline comment was a bug in 1.3.1
that has been (somewhat ;) solved.
Matthias
--
Matthias Hopf <mhopf@suse.de> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de
Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de
prev parent reply other threads:[~2006-06-19 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 17:12 git-rebase nukes multiline comments Matthias Hopf
2006-06-16 17:23 ` David Kowis
2006-06-16 17:55 ` David Kowis
2006-06-19 9:36 ` Matthias Hopf
2006-06-19 9:54 ` Matthias Hopf
2006-06-16 21:25 ` Junio C Hamano
2006-06-16 21:56 ` David Kowis
2006-06-16 23:21 ` Junio C Hamano
2006-06-19 9:53 ` Matthias Hopf [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=20060619095300.GB15209@suse.de \
--to=mhopf@suse.de \
--cc=git@vger.kernel.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).