From: ac131313@localhost.cygnus.com (Andrew Cagney)
To: Jiri Smid <smid@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: i386 8-byte wide watchpoints
Date: Fri, 21 Sep 2001 09:06:00 -0000 [thread overview]
Message-ID: <20010921160551.93B1B3E0B@localhost.cygnus.com> (raw)
In-Reply-To: <s8v7kutdn72.fsf@naga.suse.cz>
>
> Index: ChangeLog
> from Jiri Smid <smid@suse.cz>
>
> * MAINTAINERS: Add myself to the write-after-approval list.
Jiri, just fyi. People try to keep un-related changes separate(1).
Additions/changes to the MAINTAINERS file are considered obvious (your
addition is very obvious and most welcome!) so they just go straight
in (another generalization is: commit a change, post a patch(2)).
If you're wondering, I personally keep track of this by having
multiple GDB source trees, one for each change I submit. Before going
on a hacking frenzy, I'll `tar cf - src | tar xpf -` a clean tree and
then hack away.
enjoy,
Andrew
(1) People also do things like: pick all the obvious bits of a change
out and then commit them separatly as they don't need approval; or get
approval in principal for not-so-obvious changes and thus make them
obvious :-)
(2) Unless it is a really embarising foobar to the ChangeLog file or
...
prev parent reply other threads:[~2001-09-21 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 0:20 Jiri Smid
2001-09-21 9:06 ` Andrew Cagney [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=20010921160551.93B1B3E0B@localhost.cygnus.com \
--to=ac131313@localhost.cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=smid@suse.cz \
/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