From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: Re: update on ambiguous linespec branch
Date: Fri, 26 Aug 2011 01:45:00 -0000 [thread overview]
Message-ID: <m3mxex0wvt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m31uw92oxn.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 25 Aug 2011 14:53:24 -0600")
Tom> Here's my remaining to-do list. I will work on it before my break, but
Tom> probably won't finish it.
I forgot to mention that I haven't run make check -- I've just been
madly hacking away, making a few selected tests work. So, I'm sure
there are tons of regressions right now.
Tom
prev parent reply other threads:[~2011-08-26 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 20:53 Tom Tromey
2011-08-26 1:41 ` [Archer] " Joel Brobecker
2011-08-26 2:08 ` Tom Tromey
2011-08-26 1:45 ` Tom Tromey [this message]
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=m3mxex0wvt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).