From: Mark Wielaard <mark@klomp.org>
To: Timothy Wall <twall@users.sf.net>
Cc: Anthony Green <green@moxielogic.com>,
"libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>,
david.gilbert@linaro.org
Subject: Re: libffi 3.0.11 release candidate 2 available for testing
Date: Sun, 13 Nov 2011 13:29:00 -0000 [thread overview]
Message-ID: <1321190952.18216.1.camel@springer.wildebeest.org> (raw)
In-Reply-To: <05E6778C-E333-454E-8E03-A6323CEFE215@users.sf.net>
On Sun, 2011-11-13 at 07:44 -0500, Timothy Wall wrote:
> where's the original git repo again?
You never know with git do you? :)
But I get mine from: git clone git://github.com/atgreen/libffi.git
Which does seem to contain the latest changes.
Cheers,
Mark
next prev parent reply other threads:[~2011-11-13 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 4:55 Anthony Green
2011-11-13 12:45 ` Timothy Wall
2011-11-13 13:29 ` Mark Wielaard [this message]
2011-11-18 12:09 ` David Gilbert
2011-11-18 16:13 ` Anthony Green
2011-11-18 7:54 Peter Kruse
2011-11-18 15:42 ` Anthony Green
2011-11-23 8:39 ` Peter Kruse
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=1321190952.18216.1.camel@springer.wildebeest.org \
--to=mark@klomp.org \
--cc=david.gilbert@linaro.org \
--cc=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=twall@users.sf.net \
/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).