From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: "Eli Zaretskii" <eliz@gnu.org>,
romain@orebokech.com, "Štěpán Němec" <stepnem@gmail.com>,
emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r102688: Minor clean up to silence some gcc warnings.
Date: Mon, 20 Dec 2010 13:08:09 -0500 [thread overview]
Message-ID: <jwvk4j4s4ka.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ei9c34sr.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 20 Dec 2010 22:19:32 +0800")
>> I fail to see the relationship between ChangeLog changes and
>> bisecting. In any case, the way forward is to stop using ChangeLog
>> files.
> I still find the ChangeLog rather useful. Occasional extra verbiage in
> the bzr diffs and an extra minute's editing work when merging branches
> is not a large price to pay.
Agreed, which is why I'm not making any particular effort to get rid of
the ChangeLog files. But I just point out that if someone wants to fix
those pesky ChangeLog diffs, (s)he should work towards getting rid of
the ChangeLog files rather than trying to impose some constraint on how
I edit them.
Stefan
prev parent reply other threads:[~2010-12-20 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1PUCaG-00051g-NC@internal.in.savannah.gnu.org>
2010-12-19 11:41 ` /srv/bzr/emacs/trunk r102688: Minor clean up to silence some gcc warnings Romain Francoise
2010-12-19 13:59 ` Stefan Monnier
2010-12-19 15:01 ` Eli Zaretskii
2010-12-20 2:53 ` Stefan Monnier
2010-12-20 8:03 ` Štěpán Němec
2010-12-20 14:04 ` Stefan Monnier
2010-12-20 14:19 ` Chong Yidong
2010-12-20 15:31 ` /srv/bzr/emacs/trunk r102688: Minor clean up to silence somegcc warnings Drew Adams
2010-12-20 16:51 ` Karl Fogel
2010-12-20 17:18 ` Drew Adams
2010-12-20 18:05 ` Stefan Monnier
2010-12-20 18:08 ` Stefan Monnier [this message]
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=jwvk4j4s4ka.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.com \
--cc=stepnem@gmail.com \
/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.