From: Daniel Jacobowitz <drow@mvista.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: Eli Zaretskii <eliz@elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: breakpoint.c patch (prelude to pending breakpoint support)
Date: Thu, 11 Dec 2003 19:50:00 -0000 [thread overview]
Message-ID: <20031211195003.GA23834@nevyn.them.org> (raw)
In-Reply-To: <3FD8C695.6080400@redhat.com>
On Thu, Dec 11, 2003 at 02:33:41PM -0500, J. Johnston wrote:
> Eli Zaretskii wrote:
> >>Date: Thu, 11 Dec 2003 11:32:46 -0500
> >>From: "J. Johnston" <jjohnstn@redhat.com>
> >>
> >>>Is this line really that long, or did your mailer mess it up? If the
> >>>former, it needs to be reformatted.
> >>
> >>Eli, I realize you are just making a minor comment, but can I ask that
> >>gdb maintainers please start trusting me on this.
> >
> >
> >Sorry, I didn't in any way mean to say that I didn't trust you. I
> >couldn't possibly know whether what I saw was a real mistake on your
> >part or not, and I think it isn't reasonable to request me to check
> >your previous ChangeLog entries in order to decide one way or the
> >other. One popular reason for messed-up formatting is your mailer,
> >so I took care to inquire about that before assuming that what I see
> >is what you meant.
> >
> >Could we please assume that the comments you get are meant to make
> >sure the code is up to the standards, not to diminish your abilities
> >or show signs of mistrust?
> >
> >
>
> No need to apologize. I wasn't trying to imply that you didn't trust me
> nor was I offended in any way. The request was to all gdb global
> maintainers out there. The comment about the line length for my ChangeLog
> entries comes up continously and I thought it was time I just pointed out
> that I am on the same page as everyone else with regards to this.
We can't stop complaining about misformated entries for everybody,
since a lot of people get them wrong - I do this routinely myself.
It's a common problem.
I think that the same rules for posting patches should apply to posting
changelog entries - it's not acceptable to post a different patch than
you'll check in, after all.
Just my two cents.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-11 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 1:11 Jeff Johnston
2003-12-11 4:09 ` Daniel Jacobowitz
2003-12-11 6:00 ` Eli Zaretskii
2003-12-11 14:21 ` Daniel Jacobowitz
2003-12-11 14:34 ` Eli Zaretskii
2003-12-12 19:05 ` J. Johnston
2003-12-11 20:36 ` Jim Blandy
2003-12-12 2:51 ` Daniel Jacobowitz
2003-12-12 6:18 ` Jim Blandy
2003-12-11 16:32 ` J. Johnston
2003-12-11 17:20 ` Eli Zaretskii
2003-12-11 19:33 ` J. Johnston
2003-12-11 19:50 ` Daniel Jacobowitz [this message]
2003-12-12 16:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031211195003.GA23834@nevyn.them.org \
--to=drow@mvista.com \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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