From: Andrew Cagney <ac131313@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Move find_frame_addr_in_frame_chain() to varobj.c
Date: Mon, 25 Nov 2002 11:09:00 -0000 [thread overview]
Message-ID: <3DE27582.90005@redhat.com> (raw)
In-Reply-To: <3DE26F28.59C8E54B@redhat.com>
> Say, is this a policy change?
> Are we substituting [commit] for [PATCH]?
There isn't a policy.
People have observed though that `patch' is pretty ambigous - some
people use it when subitting something for aproval, others when
committing a patch, others ...
So I'm just trying to avoid it.
Andrew
prev parent reply other threads:[~2002-11-25 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-24 6:19 Andrew Cagney
2002-11-25 10:42 ` Michael Snyder
2002-11-25 11:09 ` 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=3DE27582.90005@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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