unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: ChangeLogs
Date: Thu, 19 Mar 2015 07:25:42 +0000	[thread overview]
Message-ID: <87vbhxwirt.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <m23851eizi.fsf@newartisans.com> (John Wiegley's message of "Wed,  18 Mar 2015 22:58:25 -0500")

>>>>> John Wiegley <johnw@newartisans.com> writes:
>>>>> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

 >>> * lisp/leim/quail/hangul.el
 >>> * lisp/progmodes/cperl-mode.el: Use delete-char instead of
 >>> delete-backward-char, fixes compilation warnings.

 >> The above doesn't use the right syntax.  The right syntax looks like

 >> * <filename> (<functionname>): blabla.

 > Since we have Git now, is there a reason to keep using ChangeLogs?

	The above applies to Git log messages just the same.

	Also, it’s still deemed useful to provide ChangeLogs with proper
	releases, /and/ we’re yet to transition to the scheme which
	would generate those out of Git logs.  (See bug#19113 [1].)

[1] http://debbugs.gnu.org/19113

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A



  reply	other threads:[~2015-03-19  7:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150318194629.7043.70347@vcs.savannah.gnu.org>
     [not found] ` <E1YYJvB-0001qD-9d@vcs.savannah.gnu.org>
2015-03-19  3:18   ` [Emacs-diffs] master f469024: Use delete-char instead of delete-backward-char Stefan Monnier
2015-03-19  3:58     ` John Wiegley
2015-03-19  7:25       ` Ivan Shmakov [this message]
2015-03-19 21:39         ` ChangeLogs Paul Eggert
2015-03-19  4:59     ` [Emacs-diffs] master f469024: Use delete-char instead of delete-backward-char Vibhav Pant
2015-03-19 18:48     ` vibhavp
2015-03-19 20:04       ` Stefan Monnier
2015-03-19 20:21         ` vibhavp
2015-03-19 20:57           ` Stefan Monnier

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=87vbhxwirt.fsf_-_@violet.siamics.net \
    --to=ivan@siamics.net \
    --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).