From: Mike Frysinger <vapier@gentoo.org>
To: uclinux-dev@uclinux.org
Cc: buildroot@busybox.net, crossgcc@sourceware.org, uclibc@uclibc.org
Subject: official elf2flt homepage/repo updated
Date: Thu, 24 Dec 2015 07:00:00 -0000 [thread overview]
Message-ID: <20151224070051.GG25803@vapier.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
with the demise of the cvs repo, we've moved officially to github:
https://github.com/uclinux-dev/elf2flt
this is based on the git mirror i had been previously maintaining here:
git://wh0rd.org/elf2flt.git
https://github.com/vapier/elf2flt
so if you happened to have a copy of that, you should be set to switch
over to the new location.
support will continue to use the uclinux-dev@uclinux.org mailing list.
but if people have changes they wish to merge, feel free to send pull
requests to the new location. it even has travis build testing and a
simple (for now) testsuite.
i've cross-posted to a few lists which are all in bcc to try and keep
the resulting thread on uclinux-dev. let's see how that goes ;).
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2015-12-24 7:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151224070051.GG25803@vapier.lan \
--to=vapier@gentoo.org \
--cc=buildroot@busybox.net \
--cc=crossgcc@sourceware.org \
--cc=uclibc@uclibc.org \
--cc=uclinux-dev@uclinux.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).