From: Kris Van Hees <kris.van.hees@oracle.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>,
frysk@sourceware.org, cagney@sourceware.org
Subject: Re: frysk-top ChangeLog
Date: Wed, 11 Jul 2007 13:47:00 -0000 [thread overview]
Message-ID: <20070711134714.GC11657@ca-server1.us.oracle.com> (raw)
In-Reply-To: <4694DC53.4040903@redhat.com>
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.
I also have to second Mark's opinion that simply removing his entry
rather than talking about it seems a bit harsh. Obviously, Mark did
feel that there was a good reason to have a changelog entry for the
patch he commited. That alone should be enough reason to make this a
matter to discuss.
Cheers,
Kris
On Wed, Jul 11, 2007 at 09:34:11AM -0400, Andrew Cagney wrote:
> htdocs do not have changelogs entries; they never have.
>
> Something more interesting is why htdocs do not get posted to frysk-cvs;
> I'm investigating.
>
> Mark Wielaard wrote:
> >Hi Andrew,
> >
> >On Tue, 2007-07-10 at 16:00 +0000, cagney@sourceware.org wrote:
> >
> >>Log message:
> >> Remove stray changelog entry.x
> >>
> >>Patches:
> >>http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-top/ChangeLog.diff?cvsroot=frysk&r1=1.87&r2=1.88
> >>
> >
> >Why did you remove my ChangeLog entry? I explicitly put that there to
> >document the change and because other ChangeLog entries for htdocs
> >related files also went into that file. If you feel they are better
> >documented in some other ChangeLog file please just tell me instead of
> >silently removing patches so I know why/where I should document these
> >things.
> >
> >Thanks,
> >
> >Mark
> >
>
next prev parent reply other threads:[~2007-07-11 13:47 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 [this message]
2007-07-11 14:38 ` Mark Wielaard
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=20070711134714.GC11657@ca-server1.us.oracle.com \
--to=kris.van.hees@oracle.com \
--cc=cagney@redhat.com \
--cc=cagney@sourceware.org \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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).