From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [commit] Last major piece of fork tracing - vfork/exec
Date: Fri, 22 Aug 2003 19:36:00 -0000 [thread overview]
Message-ID: <200308221936.h7MJaQDR016146@duracef.shout.net> (raw)
> The release isn't been held up for the gdb.cp rename, it happened to
> slip nicely into the schedule. If it's not done by Sunday, I can easily
> do it myself.
I am planning to do it in HEAD this evening. I really think that
Sunday is premature for doing it on the branch. :(
However, if you want to give me an H-Hour, I can do the grunt work
on the branch at that time. Say, 4:00 PM on Sunday UTC?
Michael C
next reply other threads:[~2003-08-22 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 19:36 Michael Elizabeth Chastain [this message]
2003-08-22 22:07 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-08-25 1:19 Michael Elizabeth Chastain
2003-08-25 15:06 ` Andrew Cagney
2003-08-22 15:53 Michael Elizabeth Chastain
2003-08-22 18:40 ` Andrew Cagney
2003-08-17 20:19 Daniel Jacobowitz
2003-08-18 15:46 ` Andrew Cagney
2003-08-22 15:32 ` Andrew Cagney
2003-08-22 21:20 ` 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=200308221936.h7MJaQDR016146@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=drow@mvista.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