git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org, "Eric Wong" <normalperson@yhbt.net>,
	"Sam Vilain" <sam.vilain@catalyst.net.nz>,
	kha@treskal.com, ae@op5.se
Subject: Re: [PATCH 1/2] git-svn: don't append extra newlines at the end of commit messages.
Date: Fri, 13 Jun 2008 12:17:44 -0400	[thread overview]
Message-ID: <32541b130806130917y23a55751tfccac0de8143ebe4@mail.gmail.com> (raw)
In-Reply-To: <7vfxrhyjqd.fsf@gitster.siamese.dyndns.org>

On 6/13/08, Junio C Hamano <gitster@pobox.com> wrote:
> Avery Pennarun <apenwarr@gmail.com> writes:
>  > Instead, let's remove all trailing whitespace from the git commit on the way
>  > through to svn.
>
> Perl part of the code looks fine but I am unsure if we like the
>  ramifications of this patch on existing git-svn managed repositories.
>  Doesn't this change the commit object name on our end for almost all of
>  them?

Unless I got confused while coding this (I don't think I did), this
should *not* affect existing or re-imported svn or git-svn
repositories.  It only removes trailing whitespace the first time a
git commit is sent into svn, which should happen only once for a brand
new commit by someone who has made it in git and is now dcommiting it
to svn.

Naturally, the dcommit round-trip *always* produces a new sha1 hash
for that commit anyhow because of the added git-svn-id: line.  After
this change, the sha1 will be different than it would have been
before, but it will still be the same for anyone who checks out from
svn again with git-svn.

Thanks,

Avery

  parent reply	other threads:[~2008-06-13 16:19 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 [this message]
2008-06-13  7:23 ` Andreas Ericsson
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=32541b130806130917y23a55751tfccac0de8143ebe4@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kha@treskal.com \
    --cc=normalperson@yhbt.net \
    --cc=sam.vilain@catalyst.net.nz \
    /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).