git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guilhem Bonnefille" <guilhem.bonnefille@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: "Richard MUSIL" <richard.musil@st.com>, git@vger.kernel.org
Subject: Re: git-svn: commit author x commit committer issue
Date: Wed, 22 Aug 2007 12:07:58 +0200	[thread overview]
Message-ID: <8b65902a0708220307g2cb4b290s9bbf4603af7489fa@mail.gmail.com> (raw)
In-Reply-To: <20070816092002.GD16849@muzzle>

On 8/16/07, Eric Wong <normalperson@yhbt.net> wrote:
> Richard MUSIL <richard.musil@st.com> wrote:
> > Normally, when patch is applied, git distinguishes commit author and
> > commit committer (relying on info from patch).
> > However, after the patches are committed to svn repository using:
> > git-svn dcommit
> > author and committer data are set to same values (or at least time and
> > date, I cannot verify it for names).
> > I wonder if there is any reason for this behavior, because I would
> > definitely like to keep original commit info (which came from patch) in
> > my git repository.
>
> I try to keep commits made to SVN using git-svn as much like commits
> made using other SVN clients as much as possible.
>
> Two people using git-svn (in its recommended fashion and maintaining
> linear history) can have identical SHA1s in their repository even if
> those two repositories had never seen each other before.  Consistency
> is good.
>
> I also want to avoid creating extra junk on the SVN repository which I
> don't personally consider very important.  SVK does stuff like that with
> merges, and only SVK understands the metadata it uses.  I prefer
> transparency.

Instead of using SVN metadata, why not store the missing information
like git-svn store the SVN rev id. (in the commit log as I know).

-- 
Guilhem BONNEFILLE
-=- #UIN: 15146515 JID: guyou@im.apinc.org MSN: guilhem_bonnefille@hotmail.com
-=- mailto:guilhem.bonnefille@gmail.com
-=- http://nathguil.free.fr/

  parent reply	other threads:[~2007-08-22 10:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 13:46 git-svn: commit author x commit committer issue Richard MUSIL
2007-08-08 15:42 ` Quy Tonthat
2007-08-08 17:13 ` Peter Baumann
2007-08-09  9:45   ` Richard MUSIL
2007-08-16  9:20 ` Eric Wong
2007-08-16 12:13   ` Richard MUSIL
2007-08-17  7:58     ` Eric Wong
2007-08-22 10:07   ` Guilhem Bonnefille [this message]
2007-08-22 10:17     ` Guilhem Bonnefille
2007-08-22 21:34       ` Junio C Hamano
2007-08-23  5:05         ` Eric Wong
2007-08-23  8:51           ` Richard MUSIL

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=8b65902a0708220307g2cb4b290s9bbf4603af7489fa@mail.gmail.com \
    --to=guilhem.bonnefille@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    --cc=richard.musil@st.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).