unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Subject: Re: ChangeLogs in the elpa branch
Date: Mon, 26 Sep 2011 11:52:24 -0400	[thread overview]
Message-ID: <jwvipofgvbw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8739fj5qmd.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 26 Sep 2011 09:23:54 -0500")

> I find them useful and "bzr log" doesn't always work as well as plain
> text comments.  For instance it's much harder to go back and edit a
> published VCS log than a ChangeLog file.

They each have their advantage and inconvenients, but they're not
sufficient to justify keeping both.  So for the "edit the VCS log",
you'll want to file a feature request with the Bazaar guys (or rather,
add your voice to the existing bug number).

> `C-x 4 a' would need a parallel command to edit the built-in ChangeLog.

Yes, C-x 4 a will need work so it's useful even without a ChangeLog.
Maybe a simple way to do that is to have *VC-Log* save itself into
a .changelog file which gets auto-removed upon commit, and then have C-x
4 use/create such a .changelog file (at the root of the checkout) if there's
no ChangeLog.  This has been discussed already in the past, but there
hasn't been any progress, so I hope this change to `elpa' will be
a motivating factor.


        Stefan



  reply	other threads:[~2011-09-26 15:52 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 [this message]
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
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=jwvipofgvbw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).