From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [dictionary] commit for 2003-03-06
Date: Fri, 07 Mar 2003 14:58:00 -0000 [thread overview]
Message-ID: <3E68B3A3.10805@redhat.com> (raw)
In-Reply-To: <ro1y93sf15j.fsf@jackfruit.Stanford.EDU>
> Following Andrew's lead,
It wasn't my lead. GCC pretty much run branches this way.
> I'm going to try to remember to post my
> commits to carlton_dictionary-branch. They won't always be the
> prettiest commits: I usually commit once at the end of each day that
> I've done any work on the branch, assuming that I leave it in a
> working state (which I almost always do!); this means that a commit
> may contain something that I plan to continue the next day, and it
> also may contain bits of unrelated tasks that I'm working on. Also,
> the ChangeLogs aren't great: they're written in a way that is easy to
> generate, as opposed to a way that is easiest to review years in the
> future.
Even if it doesn't build, do you care?
Andrew
next prev parent reply other threads:[~2003-03-07 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 0:53 David Carlton
2003-03-07 14:40 ` Daniel Jacobowitz
2003-03-07 16:53 ` David Carlton
2003-03-07 18:01 ` David Carlton
2003-03-07 14:58 ` Andrew Cagney [this message]
2003-03-07 17:08 ` David Carlton
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=3E68B3A3.10805@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--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