From: Andreas Ericsson <ae@op5.se>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 1/2] git-svn: don't append extra newlines at the end of commit messages.
Date: Fri, 13 Jun 2008 09:23:01 +0200 [thread overview]
Message-ID: <48522055.6060006@op5.se> (raw)
In-Reply-To: <1213312251-8081-1-git-send-email-apenwarr@gmail.com>
Avery Pennarun wrote:
> In git, all commits end in exactly one newline character. In svn, commits
> end in zero or more newlines. Thus, when importing commits from svn into
> git, git-svn always appends two extra newlines to ensure that the
> git-svn-id: line is separated from the main commit message by at least one
> blank line.
>
> Combined with the terminating newline that's always present in svn commits
> produced by git, you usually end up with two blank lines instead of one
> between the commit message and git-svn-id: line, which is undesirable.
>
> Instead, let's remove all trailing whitespace from the git commit on the way
> through to svn.
>
I'm not familiar with git-svn, and my perl is pretty weak as it is.
Are you proposing to remove extra whitespace from git commits when they are
sent back to svn via dcommit? If so, wouldn't it be better to always strip
extra newlines when importing from svn so they're never there in the first
place?
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-06-13 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 23:10 [PATCH 1/2] git-svn: don't append extra newlines at the end of commit messages Avery Pennarun
2008-06-12 23:10 ` [PATCH 2/2] git-svn: test that extra blank lines aren't inserted in " Avery Pennarun
2008-06-13 5:41 ` [PATCH 1/2] git-svn: don't append extra newlines at the end of " Junio C Hamano
2008-06-13 6:29 ` Karl Hasselström
2008-06-13 16:17 ` Avery Pennarun
2008-06-13 7:23 ` Andreas Ericsson [this message]
2008-06-13 8:09 ` Karl Hasselström
2008-06-14 8:43 ` Karl Hasselström
2008-06-13 16:23 ` Avery Pennarun
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=48522055.6060006@op5.se \
--to=ae@op5.se \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).