From: Bastien <bzg@altern.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: ChangeLogs in the elpa branch
Date: Tue, 27 Sep 2011 07:22:49 +0200 [thread overview]
Message-ID: <874nzypniu.fsf@gnu.org> (raw)
In-Reply-To: <jwvty7zdynz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 26 Sep 2011 13:08:16 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> That's not written in stone. CVS can edit its commit logs, and there's
> no reason the same can't be done for other revision control systems.
At least for git, you can edit the last commit message with a simple
~$ git commit --amend
But editing the commit logs beyond that goes against a principle that
is somewhat carved in stone: "Don't modify the commit logs history."
I don't know how bzr devs feel about this.
--
Bastien
next prev parent reply other threads:[~2011-09-27 5:22 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 [this message]
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=874nzypniu.fsf@gnu.org \
--to=bzg@altern.org \
--cc=emacs-devel@gnu.org \
--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).