From: Andrew STUBBS <andrew.stubbs@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Fix TUI null pointer dereference
Date: Tue, 01 Nov 2005 17:06:00 -0000 [thread overview]
Message-ID: <43679FEA.9020506@st.com> (raw)
In-Reply-To: <20051101170146.GA31019@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Tue, Nov 01, 2005 at 04:56:06PM +0000, Andrew STUBBS wrote:
>
>>Sorry I have not sent this before. I assumed the [commit] messages were
>>just from people who had not previously posted a [patch].
>
>
> No problem.
>
> Normally [commit] is "I'm going to commit this". All I'm asking for is
> a reply to the approval saying "I have now committed this".
>
> The point is just for bookkeeping; easier to keep track of which
> approved patches have been checked in and which have been dropped, if
> there's a commit message in the original thread. We've had some
> problems in the past with approved patches being lost.
>
Sorry, I've now misundertood twice. Ah well, we live and learn.
prev parent reply other threads:[~2005-11-01 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 16:58 Andrew STUBBS
2005-11-01 17:01 ` Daniel Jacobowitz
2005-11-01 17:06 ` Andrew STUBBS [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=43679FEA.9020506@st.com \
--to=andrew.stubbs@st.com \
--cc=drow@false.org \
--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