git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Quirk" <richard.quirk@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Avery Pennarun" <apenwarr@gmail.com>,
	"Eric Wong" <normalperson@yhbt.net>,
	"Sam Vilain" <sam@vilain.net>,
	git@vger.kernel.org, "Avery Pennarun" <apenwarr@versabanq.com>
Subject: Re: [PATCH 2/3] git-svn: Add --add-author-from option.
Date: Wed, 16 Apr 2008 21:11:56 +0200	[thread overview]
Message-ID: <cac9e4380804161211h1f49dc0bg810cfa9c0d47af5d@mail.gmail.com> (raw)
In-Reply-To: <7v3aplsl3p.fsf@gitster.siamese.dyndns.org>

On Wed, Apr 16, 2008 at 8:36 PM, Junio C Hamano <gitster@pobox.com> wrote:

>  For example, CVS honors LOGNAME to allow you to "lie" who the author of a
>  change was, which is the behaviour inherited from RCS.  I have to wonder
>  if SVN has a similar mechanism to tell it "Excuse me, but I am just a
>  secretary recording changes for my boss."

The author is stored as a property of the commit, so you can set alter
it with something like `svn propset --revprop -r N svn:author NAME
REPO_URL` providing you have server-side revision property changes
enabled.

  parent reply	other threads:[~2008-04-16 19:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  1:04 [PATCH 1/3] git-svn: add documentation for --use-log-author option apenwarr
2008-04-16  1:04 ` [PATCH 2/3] git-svn: Add --add-author-from option apenwarr
2008-04-16  1:04   ` [PATCH 3/3] git-svn: add documentation for " apenwarr
2008-04-16  4:33   ` [PATCH 2/3] git-svn: Add " Junio C Hamano
2008-04-16 16:46     ` Avery Pennarun
2008-04-16 18:36       ` Junio C Hamano
2008-04-16 18:45         ` Avery Pennarun
2008-04-16 19:11         ` Richard Quirk [this message]
2008-04-16 19:23         ` Dmitry Potapov
2008-04-16 22:24           ` Sam Vilain
2008-04-16 22:34             ` Avery Pennarun
2008-04-17  4:36   ` Eric Wong

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=cac9e4380804161211h1f49dc0bg810cfa9c0d47af5d@mail.gmail.com \
    --to=richard.quirk@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=apenwarr@versabanq.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=normalperson@yhbt.net \
    --cc=sam@vilain.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 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).