From: Christian Thalinger <twisti@complang.tuwien.ac.at>
To: mauve-patches ml <mauve-patches@sourceware.org>
Subject: Re: build directory support, final commit
Date: Wed, 25 Jun 2008 14:58:00 -0000 [thread overview]
Message-ID: <1214405879.28631.4.camel@cthalinger> (raw)
In-Reply-To: <1214405411.4472.22.camel@cthalinger>
On Wed, 2008-06-25 at 16:50 +0200, Christian Thalinger wrote:
> Hi!
>
> This commit finishes my changes to support build directory support. I
> have tested these change about 20 days[1] now with our testing framework
[1]
http://c1.complang.tuwien.ac.at/pipermail/cacao-testresults/2008-June/thread.html
prev parent reply other threads:[~2008-06-25 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 14:51 Christian Thalinger
2008-06-25 14:58 ` Christian Thalinger [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=1214405879.28631.4.camel@cthalinger \
--to=twisti@complang.tuwien.ac.at \
--cc=mauve-patches@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).