From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Michael Albinus <michael.albinus@gmx.de>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: ChangeLogs in the elpa branch
Date: Tue, 27 Sep 2011 21:02:04 +0900 [thread overview]
Message-ID: <877h4u2nyb.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CAAeL0SSXr_574diUj-jTr-0W-M3nRbaV27si8Mvw9TDwwPYpQA@mail.gmail.com>
Juanma Barranquero writes:
> On Tue, Sep 27, 2011 at 09:10, Glenn Morris <rgm@gnu.org> wrote:
> > I disagree, I think people take more care with ChangeLogs.
>
> I'm with Glenn again. And part of the fact is, IMO, the immediacy of
> writting the commit logs. I'd bet not many people write them at a
> leisurely pace before even starting the commit.
That's because not many people write ChangeLogs at a leisurely pace
before even starting the commit. Anyway, the right time to write log
message (of either type) is before starting to code. ;-)
This particular issue is easy enough to solve, though.
1. Disable the log message prompt in the vc-commit code.
2. Add -F .emacs-vc-commit-log (or whatever the equivalent is in .bzr)
to the commit command (and maybe some sort of "up-to-date" check on
that file).
3. Have "C-x 4 a" look for that file as well as/instead of ChangeLog,
and create it (in preference to ChangeLog) if neither is found.
There are some rough edges there, but once the basic idea is
implemented, you'll never notice you're not writing ChangeLogs any
more.
next prev parent reply other threads:[~2011-09-27 12:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:09 ChangeLogs in the elpa branch Michael Albinus
2011-09-26 9:56 ` Julien Danjou
2011-09-26 10:23 ` Lars Magne Ingebrigtsen
2011-09-26 10:35 ` Michael Albinus
2011-09-26 14:23 ` Ted Zlatanov
2011-09-26 15:52 ` Stefan Monnier
2011-09-26 16:49 ` Ted Zlatanov
2011-09-26 21:13 ` Richard Stallman
2011-09-26 11:46 ` Dave Abrahams
2011-09-26 13:03 ` Stefan Monnier
2011-09-26 13:49 ` Michael Albinus
2011-09-26 16:26 ` Glenn Morris
2011-09-26 16:38 ` Lars Magne Ingebrigtsen
2011-09-26 19:18 ` Andreas Schwab
2011-09-26 17:06 ` Eli Zaretskii
2011-09-26 17:08 ` Stefan Monnier
2011-09-26 21:18 ` Michael Albinus
2011-09-26 21:27 ` Lars Magne Ingebrigtsen
2011-09-27 3:10 ` Michael Albinus
2011-09-27 5:22 ` Bastien
2011-09-27 8:57 ` Andreas Schwab
2011-09-27 9:04 ` Bastien
2011-09-27 9:25 ` Eli Zaretskii
2011-09-27 13:00 ` Stefan Monnier
2011-09-27 7:10 ` Glenn Morris
2011-09-27 9:05 ` Juanma Barranquero
2011-09-27 9:45 ` joakim
2011-09-27 12:02 ` Stephen J. Turnbull [this message]
2011-09-27 13:05 ` Stefan Monnier
2011-09-27 9:00 ` Juanma Barranquero
2011-09-27 12:24 ` Thien-Thi Nguyen
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=877h4u2nyb.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=michael.albinus@gmx.de \
--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).