From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
Subject: Re: Nonsense in gnus-uu.el
Date: Wed, 15 Apr 2015 15:37:03 +0200 [thread overview]
Message-ID: <m3fv81jyww.fsf@gnus.org> (raw)
In-Reply-To: <552E6812.6060606@yandex.ru> (Dmitry Gutov's message of "Wed, 15 Apr 2015 16:30:58 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 04/15/2015 04:20 PM, Lars Magne Ingebrigtsen wrote:
>
>> Hm. What are the commit rules these days with the ChangeLog-less setup?
>> It's probably on a web page somewhere...
>
> It's in CONTRIBUTE.
- If you use Emacs VC, one way to format ChangeLog entries is to create
a top-level ChangeLog file manually, and update it with 'C-x 4 a' as
usual. Do not register the ChangeLog file under git; instead, use
'C-c C-a' to insert its contents into into your *vc-log* buffer.
Or if `log-edit-hook' includes `log-edit-insert-changelog' (which it
does by default), they will be filled in for you automatically.
Aha. Okidoke...
- Alternatively, you can use the vc-dwim command to maintain commit
messages. When you create a source directory, run the shell command
'git-changelog-symlink-init' to create a symbolic link from
ChangeLog to .git/c/ChangeLog. Edit this ChangeLog via its symlink
with Emacs commands like 'C-x 4 a', and commit the change using the
shell command 'vc-dwim --commit'. Type 'vc-dwim --help' for more.
I don't have any shell command called git-changelog-symlink-init,
apparently.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2015-04-15 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 14:42 Nonsense in gnus-uu.el Stefan Monnier
2015-04-15 13:20 ` Lars Magne Ingebrigtsen
2015-04-15 13:30 ` Dmitry Gutov
2015-04-15 13:37 ` Lars Magne Ingebrigtsen [this message]
2015-04-15 17:53 ` Paul Eggert
2015-04-15 17:55 ` Lars Magne Ingebrigtsen
2015-04-15 22:59 ` Paul Eggert
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=m3fv81jyww.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).