unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: bug#881: patch for bug #881
Date: Wed, 06 Jan 2010 08:22:33 +0100	[thread overview]
Message-ID: <87637fg0jq.fsf@telefonica.net> (raw)
In-Reply-To: 201001060700.o06706Sw006855@godzilla.ics.uci.edu

Dan Nicolaescu <dann@ics.uci.edu> writes:

>   > > When applying changes by non-committers, should we use the --author
>   > > option of commit?
>   > 
>   > Yes, that would be good.  We will even have to require it if/when we
>   > decide to auto-generate the ChangeLog file.
>   >
>   > > If so, is that supported by VC?
>   > 
>   > I don't think so,
>
> How should it work? We don't have any nice generic mechanism/UI for
> doing VC backend specific things in the commit buffer.

Maybe something like

##--author="John Doe <joe@doe.com>"
<<rest of commit message here>>

BTW, psvn and similar packages put some explicative text on top of the
buffer plus the list of files to be committed:

## Lines starting with '## ' will be removed from the log message.
## File(s) to commit recursively:
## foo/bar.org

I think this would be useful specially now that it is important to
commit all files at once. So VC would show:

## Lines starting with '## ' will be removed from the log message.
## Lines starting with '##-' indicate extra arguments for the command.
## File(s) to commit recursively:
## foo/bar.org

-- 
Óscar





  reply	other threads:[~2010-01-06  7:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wrzwp5gd.fsf@stupidchicken.com>
2010-01-06  0:43 ` bug#881: patch for bug #881 Juanma Barranquero
2010-01-06  3:35   ` Karl Fogel
2010-01-06  4:12     ` Juanma Barranquero
2010-01-06  4:19       ` Karl Fogel
2010-01-06 10:12         ` Juanma Barranquero
2010-01-06 18:15           ` Eli Zaretskii
2010-01-06 20:43             ` Juanma Barranquero
2010-01-07  4:14               ` Eli Zaretskii
2010-01-07  9:13                 ` Juanma Barranquero
2010-01-06  4:13   ` Eli Zaretskii
2010-01-06  4:34   ` Stefan Monnier
2010-01-06  7:00     ` Dan Nicolaescu
2010-01-06  7:22       ` Óscar Fuentes [this message]
2010-01-06  9:34         ` Stephen J. Turnbull
2010-01-06 14:20       ` Stefan Monnier
2010-01-06 18:29         ` Dan Nicolaescu
2010-01-06 20:19           ` Stefan Monnier
2010-01-07 17:09             ` Dan Nicolaescu
2010-01-07 20:07               ` Stefan Monnier
2010-01-06 18:29         ` Eli Zaretskii
2010-01-06 18:52           ` Óscar Fuentes
2010-01-06 20:20             ` Stefan Monnier
2010-01-06 20:40               ` Eli Zaretskii
2010-01-07 15:33                 ` Juanma Barranquero
2010-01-07 17:15                   ` bzr --fixes [was Re: bug#881: patch for bug #881] Glenn Morris
2010-01-07 20:12                     ` Juanma Barranquero
2010-01-07 20:34                       ` bzr --fixes Glenn Morris
2010-01-07 22:35                         ` Juanma Barranquero
2010-01-08  9:01                           ` Eli Zaretskii
2010-01-08  8:27                         ` Eli Zaretskii
2010-01-06 20:00         ` Committing other people's changes (was: bug#881: patch for bug #881) Reiner Steib
2010-01-16 21:50     ` bug#881: patch for bug #881 Chong Yidong
2010-01-16 21:52       ` Juanma Barranquero
2010-01-16 22:30         ` Chong Yidong
2010-01-17  9:38           ` Dan Nicolaescu

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87637fg0jq.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).