From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@kealia.com>
Cc: David Lecomber <david@streamline-computing.com>,
gdb-patches@sources.redhat.com
Subject: Re: Large array printing patch for Fortran
Date: Mon, 06 Oct 2003 16:51:00 -0000 [thread overview]
Message-ID: <20031006165125.GA21526@nevyn.them.org> (raw)
In-Reply-To: <yf2he2m9ux2.fsf@hawaii.kealia.com>
On Mon, Oct 06, 2003 at 09:45:45AM -0700, David Carlton wrote:
> On Mon, 29 Sep 2003 18:35:17 +0100, David Lecomber <david@streamline-computing.com> said:
>
> > This patch sets the formatting correctly in the patch I previously
> > applied.
>
> > 2003-09-29 David Lecomber <dsl@sources.redhat.com>
>
> > * f-valprint.c: Reformatting
>
> I'm sorry you find it frustrating that people don't approve your
> patches as quickly as they should. But you still have to wait for
> approval before committing them. I've told you this before, Daniel
> has told you this before. If you don't like waiting, nag people;
> don't just go ahead and commit stuff.
>
> There are two things wrong with your ChangeLog entry; I'm in a bad
> enough mood that I'm not going to tell you what they are. Look
> through other ChangeLog entries, see how yours is different from
> theirs. (And, while you're at it, look at what's wrong with your
> ChangeLog entry from 2003-09-15, too.) Then, post the diffs here and
> WAIT FOR SOMEBODY TO GIVE YOU EXPLICIT APPROVAL TO COMMIT THEM.
(A) I approved this patch in private.
(B) It's an obvious, withspace only patch so I didn't feel the need to
copy the list when I approved it.
(C) As a write-after-approval maintainer he is allowed to commit truly
obvious patches. Which this will be once he gets changelog style down.
I'm sorry I didn't post the approval in triplicate to the list.
David L, the problems David C refers to:
- Generally include the names of modified functions, unless you're
globally touching the whole file.
- ChangeLog entries end with a full stop.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-06 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 14:36 David Lecomber
2003-09-15 15:58 ` Daniel Jacobowitz
2003-09-15 20:40 ` David Lecomber
2003-09-15 20:52 ` Daniel Jacobowitz
2003-09-29 17:35 ` David Lecomber
2003-10-06 16:45 ` David Carlton
2003-10-06 16:51 ` Daniel Jacobowitz [this message]
2003-10-06 16:56 ` David Carlton
2003-10-06 18:50 ` 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=20031006165125.GA21526@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.com \
--cc=david@streamline-computing.com \
--cc=gdb-patches@sources.redhat.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