From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Mark Kettenis <kettenis@wins.uva.nl>, gdb-patches@sources.redhat.com
Subject: Re: SETPGRP and autoconf
Date: Mon, 30 Jul 2001 15:48:00 -0000 [thread overview]
Message-ID: <3B65E437.9020502@cygnus.com> (raw)
In-Reply-To: <20010730150903.A32225@nevyn.them.org>
> Since no one objected, I've committed this to the trunk. I don't know
> what rules we're using for the branch; can I just move it there too?
Does it fix a real bug?
Andrew
next prev parent reply other threads:[~2001-07-30 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010725162420.A13860@nevyn.them.org>
[not found] ` <200107261040.f6QAe2T05377@delius.kettenis.local>
[not found] ` <20010726084450.A2941@nevyn.them.org>
[not found] ` <3B60505D.5080304@cygnus.com>
2001-07-27 10:21 ` Daniel Jacobowitz
2001-07-27 13:09 ` Andrew Cagney
2001-07-27 13:33 ` Andrew Cagney
2001-07-27 13:42 ` Daniel Jacobowitz
2001-07-30 15:09 ` Daniel Jacobowitz
2001-07-30 15:48 ` Andrew Cagney [this message]
2001-07-30 15:52 ` Daniel Jacobowitz
2001-07-30 15:58 ` Andrew Cagney
2001-07-30 15:59 ` Daniel Jacobowitz
2001-07-31 8:51 ` Andrew Cagney
2001-08-02 14:31 ` Daniel Jacobowitz
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=3B65E437.9020502@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/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