From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] deal with vector return value for ppc68
Date: Tue, 08 Nov 2005 17:46:00 -0000 [thread overview]
Message-ID: <20051108101700.2400a596@ironwood.lan> (raw)
In-Reply-To: <200511071343.43099.pgilliam@us.ibm.com>
On Mon, 7 Nov 2005 13:43:43 -0800
Paul Gilliam <pgilliam@us.ibm.com> wrote:
> OK to commit to 6.4 branch?
It's okay with me, but Joel is the one who sets the commit policy for the
release branch. (In other words, make sure it's okay with Joel first...)
> I have never committed to a branch, so I would appreciate some pointers.
Check out the branch, apply your patch to the branch, add suitable
ChangeLog entries, and then commit.
Kevin
next prev parent reply other threads:[~2005-11-08 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 23:47 Paul Gilliam
2005-11-02 21:59 ` Kevin Buettner
2005-11-07 23:33 ` Paul Gilliam
2005-11-08 0:10 ` Paul Gilliam
2005-11-08 17:46 ` Kevin Buettner [this message]
2005-11-09 6:56 ` Joel Brobecker
2005-11-09 7:24 ` Kevin Buettner
2005-11-15 4:10 ` [COMMIT (6.4)] " Paul Gilliam
2005-11-15 4:40 ` Paul Gilliam
2005-11-02 22:42 ` [PATCH] " Daniel Jacobowitz
2005-11-03 1:31 ` Mark Kettenis
2005-11-07 21:42 ` [COMMIT] " Paul Gilliam
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=20051108101700.2400a596@ironwood.lan \
--to=kevinb@redhat.com \
--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