From: Tom Tromey <tromey@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: minor frysk cleanup
Date: Sat, 01 Mar 2008 18:27:00 -0000 [thread overview]
Message-ID: <m3d4qegxc0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1204395396.3279.31.camel@localhost.localdomain> (Mark Wielaard's message of "Sat\, 01 Mar 2008 19\:16\:36 +0100")
Mark> This looks good. Thanks.
Mark> If you have git push access please push it.
Mark> Otherwise I can do that for you.
I don't think I do.
Mark> It does help if you run make check in at least frysk-core (or make check
Mark> -k toplevel) and mention whether you see any failures (normally we
Mark> should have zero fails, at least in frysk-core).
I will run it now.
Tom
next prev parent reply other threads:[~2008-03-01 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 21:10 Tom Tromey
2008-03-01 18:16 ` Mark Wielaard
2008-03-01 18:27 ` Tom Tromey [this message]
2008-03-01 19:22 ` Mark Wielaard
2008-03-01 19:27 ` Tom Tromey
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=m3d4qegxc0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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).