From: Nathanael Nerode <neroden@twcny.rr.com>
To: gdb@sources.redhat.com
Subject: Putting in my top level changes
Date: Fri, 29 Nov 2002 13:42:00 -0000 [thread overview]
Message-ID: <20021129214149.GA507@doctormoo> (raw)
As discussed, I am going to start dropping in my top-level changes a
little bit at a time, trying making sure that there's a GDB snap done
between each small set of changes. The first two little changes went
in today.
Given the glacial rate at which gcc is moving, I expect I'll have src in
sync with the branch I'm working on in gcc before the branch lands, even
when I'm only dropping in a couple of changes per day.
--Nathanael
reply other threads:[~2002-11-29 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021129214149.GA507@doctormoo \
--to=neroden@twcny.rr.com \
--cc=gdb@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