all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Automatically commenting changes
Date: Wed, 26 Jan 2011 21:16:49 -0500	[thread overview]
Message-ID: <jwvy667m6za.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.2.1296057926.30134.help-gnu-emacs@gnu.org

> Sadly I am the only one using vcs (don't even get me *started* on that),
> otherwise people just send cra^H^Hode around by email and one person
> merges them into an "approved" version, similarly distributed via
> email. I then maintain my "private" subversion repo, with the merges and
> the changes that I make. Which means that 'svn blame' says I made all of
> the changes...

I see.  Many/most modern VCS can still handle such cases by
distinguishing the committer from the author.  I.e. when you commit you
can provide the name of the author of the code you're committing.
I'm not sure if "svn commit --username" can be used for that or even if
svn offers such functionality, tho it seems at least that you can
manipulate the "svn:author" property after the commit.


        Stefan


  parent reply	other threads:[~2011-01-27  2:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1295948439.29299.help-gnu-emacs@gnu.org>
2011-01-25 10:09 ` Automatically commenting changes Pascal J. Bourguignon
2011-01-26  3:32 ` Stefan Monnier
2011-01-26 13:21   ` Gary
     [not found]   ` <mailman.0.1296048116.12534.help-gnu-emacs@gnu.org>
2011-01-26 13:57     ` Richard Riley
2011-01-26 16:05       ` Gary
     [not found]       ` <mailman.2.1296057926.30134.help-gnu-emacs@gnu.org>
2011-01-26 19:54         ` Tim X
2011-01-27  2:16         ` Stefan Monnier [this message]
2011-01-26 15:55     ` Stefan Monnier
2011-01-25  9:40 Gary
2011-01-25  9:46 ` Deniz Dogan
2011-01-25 10:48   ` Gary
2011-01-25 18:38     ` Thierry Volpiatto

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=jwvy667m6za.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.