From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 19328@debbugs.gnu.org, Cameron Desautels <camdez@gmail.com>
Subject: bug#19328: [PATCH] Add mechanism to prompt about unsaved customizations
Date: Sun, 14 Dec 2014 09:02:48 -0500 [thread overview]
Message-ID: <jwvbnn6nxeb.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <8761dezbtf.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 14 Dec 2014 06:54:20 -0500")
> ...I see for example the commit 49daed60510a073062b41fa39fd7c010cb0a315e
> from Glenn has a nice summary of all the changes in subdirectories
> gathered from various ChangeLogs, but `C-c C-a' in the commit window
> doesn't bring in anything near that summary. Is there a way to
> auto-generate it or do I have to assemble it by hand?
Yes: from the *vc-dir* buffer, you need to explicitly select every file
you'll commit (instead of just saying "commit everything in this
directory"). Then C-c C-a will work. It's stupid but it's the way to
code works. Patches welcome.
Stefan
next prev parent reply other threads:[~2014-12-14 14:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 15:46 bug#19328: [PATCH] Add mechanism to prompt about unsaved customizations Cameron Desautels
2014-12-09 15:54 ` Drew Adams
2014-12-09 16:16 ` Cameron Desautels
2014-12-09 16:24 ` Drew Adams
2014-12-09 17:05 ` Cameron Desautels
2014-12-09 17:46 ` Drew Adams
2014-12-09 19:47 ` Cameron Desautels
2014-12-09 20:10 ` Drew Adams
2014-12-10 15:32 ` Ted Zlatanov
2014-12-12 1:04 ` Cameron Desautels
2014-12-12 1:40 ` Stefan Monnier
2014-12-12 1:56 ` Cameron Desautels
2014-12-12 2:36 ` Stefan Monnier
2014-12-12 2:39 ` Cameron Desautels
2014-12-13 1:17 ` Ted Zlatanov
2014-12-13 5:55 ` Stefan Monnier
2014-12-13 13:06 ` Ted Zlatanov
2014-12-13 23:23 ` Cameron Desautels
2014-12-14 11:54 ` Ted Zlatanov
2014-12-14 14:02 ` Stefan Monnier [this message]
2014-12-14 16:31 ` Ted Zlatanov
2016-02-23 11:36 ` Lars Ingebrigtsen
2014-12-12 2:48 ` Drew Adams
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=jwvbnn6nxeb.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19328@debbugs.gnu.org \
--cc=camdez@gmail.com \
--cc=rgm@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.