From: Mark Wielaard <mark@klomp.org>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: Andrew Cagney <cagney@redhat.com>, frysk@sourceware.org
Subject: Re: frysk-top ChangeLog
Date: Wed, 11 Jul 2007 14:38:00 -0000 [thread overview]
Message-ID: <1184164716.4322.36.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20070711134714.GC11657@ca-server1.us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi,
On Wed, 2007-07-11 at 06:47 -0700, Kris Van Hees wrote:
> This brings up the question: why don't htdocs have changelog entries? I
> can't see a good reason against having them, and there are benefits to
> having changelog entries for this stuff, either way.
>
> Obviously, Mark did feel that there was a good reason to have a
> changelog entry for the patch he commited.
To be honest I was just following what others do. As far as I know
htdocs changes are documented in the ChangeLog file since that is how I
found out where to document them. I also don't see much reason not to
have them. I was just surprised mine got deleted without any comment.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-11 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070710160014.27101.qmail@sourceware.org>
2007-07-11 9:54 ` Mark Wielaard
2007-07-11 13:34 ` Andrew Cagney
2007-07-11 13:47 ` Kris Van Hees
2007-07-11 14:38 ` Mark Wielaard [this message]
2007-07-11 15:12 ` Andrew Cagney
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=1184164716.4322.36.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=kris.van.hees@oracle.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.
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).