From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Why maintain old style ChangeLog?
Date: Fri, 17 Sep 2010 19:00:54 +0200 [thread overview]
Message-ID: <837hik1f09.fsf@gnu.org> (raw)
In-Reply-To: <i7056t$v09$1@dough.gmane.org>
> From: Oleksandr Gavenko <gavenkoa@gmail.com>
> Date: Fri, 17 Sep 2010 19:32:27 +0300
>
> I also ask similar question at (and not completely
> satisfied by answers):
>
> http://stackoverflow.com/questions/3712969/why-maintain-traditional-detailed-changelog-in-modern-world-with-svn-mercurial
>
>
> I read "Sending Patches for GNU Emacs" section of 'info emacs'.
>
> It contains requirement for writing ChangeLog entry
> to describe your changes.
This is not a good place to discuss requirements for how to submit
patches to Emacs. A much better place is emacs-devel@gnu.org.
You may wish to read past discussions about this issue (in the
archives).
next prev parent reply other threads:[~2010-09-17 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 16:32 Why maintain old style ChangeLog? Oleksandr Gavenko
2010-09-17 16:42 ` Deniz Dogan
2010-09-17 17:00 ` Eli Zaretskii [this message]
[not found] <mailman.0.1284741168.28175.help-gnu-emacs@gnu.org>
2010-09-17 19:00 ` Lowell Gilbert
2010-09-17 23:58 ` Tim X
2010-12-09 17:24 ` Drew Adams
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=837hik1f09.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).