Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: breakpoint.c patch (prelude to pending breakpoint support)
Date: Fri, 12 Dec 2003 16:58:00 -0000	[thread overview]
Message-ID: <7137-Fri12Dec2003185654+0200-eliz@elta.co.il> (raw)
In-Reply-To: <3FD8C695.6080400@redhat.com> (jjohnstn@redhat.com)

> Date: Thu, 11 Dec 2003 14:33:41 -0500
> From: "J. Johnston" <jjohnstn@redhat.com>
> 
>   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.

In that case, it is IMHO unreasonable to ask the maintainers to
remember such miniscule details about specific contributors.  I
suggest, like Daniel did, that you simply use the exact ChangeLog
entry in your message.  It is, after all, very easy to do: simply
always make an entry when you produce the patch to send to the list,
don't postpone that until the patch is approved.  As a side-effect,
you will not need to remember all the changes you did back then with
their reasons.


      parent reply	other threads:[~2003-12-12 16:58 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
2003-12-12 16:58         ` Eli Zaretskii [this message]

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=7137-Fri12Dec2003185654+0200-eliz@elta.co.il \
    --to=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