From: Uwe Brauer <oub@mat.ucm.es>
To: help-gnu-emacs@gnu.org
Subject: Re: vc-next-action or vc-dir, optionally allows to change the user?
Date: Fri, 24 Jun 2022 17:04:13 +0200 [thread overview]
Message-ID: <87iloqw1aq.fsf@mat.ucm.es> (raw)
In-Reply-To: 87r13ew318.fsf@mat.ucm.es
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:
>> On 24.06.2022 16:20, Uwe Brauer wrote:
>> Try adding the "Author:" header at the top when writing the commit message.
> Thanks that works, however if want to say commit three or 4 changes
> this way, it would be nice to have this a bit more automatised.
> I debugged vc-checkin and can see where it grabs the user name and address.
> Another approach would be to set the user variable locally for that
> repository to a different value. But this is not a lisp solution but
> one that depends on the underlying vc system
It seems that
(setq log-edit-setup-add-author t)
Is a bit helpful
--
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-06-24 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 13:20 vc-next-action or vc-dir, optionally allows to change the user? Uwe Brauer
2022-06-24 13:36 ` Dmitry Gutov
2022-06-24 14:26 ` Uwe Brauer
2022-06-24 15:00 ` Dmitry Gutov
2022-06-24 15:12 ` [a bug, with log-edit-setup-add-author?] (was: vc-next-action or vc-dir, optionally allows to change the user?) Uwe Brauer
2022-06-24 15:24 ` [culprit found] (was: [a bug, with log-edit-setup-add-author?]) Uwe Brauer
2022-06-24 15:04 ` Uwe Brauer [this message]
2022-06-24 15:32 ` vc-next-action or vc-dir, optionally allows to change the user? Jean Louis
2022-06-24 15:46 ` Uwe Brauer
2022-06-25 6:49 ` Jean Louis
2022-06-25 9:45 ` Dmitry Gutov
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=87iloqw1aq.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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.
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).