From: Lowell Gilbert <lgusenet@be-well.ilk.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Why maintain old style ChangeLog?
Date: Fri, 17 Sep 2010 15:00:26 -0400 [thread overview]
Message-ID: <44iq24i4ad.fsf@be-well.ilk.org> (raw)
In-Reply-To: mailman.0.1284741168.28175.help-gnu-emacs@gnu.org
Oleksandr Gavenko <gavenkoa@gmail.com> writes:
> But back to the original question.
>
> Does need prepare ChangeLog entry for patch at current time?
I'm not sure what you mean exactly, but I suspect the answer should be
"not in most environments, but definitely in some environments."
> And does need maintain ChangeLog at all in view
> of modern VCS tools?
In situations where someone may have access to the source code but not
the VCS, maintaining a changelog can be a very considerate thing to do.
next parent reply other threads:[~2010-09-17 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1284741168.28175.help-gnu-emacs@gnu.org>
2010-09-17 19:00 ` Lowell Gilbert [this message]
2010-09-17 23:58 ` Why maintain old style ChangeLog? Tim X
2010-12-09 17:24 ` Drew Adams
2010-09-17 16:32 Oleksandr Gavenko
2010-09-17 16:42 ` Deniz Dogan
2010-09-17 17:00 ` Eli Zaretskii
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=44iq24i4ad.fsf@be-well.ilk.org \
--to=lgusenet@be-well.ilk.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).