From: ams@gnu.org (Alfred M. Szmidt)
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: mattst88@gmail.com, viriketo@gmail.com, libc-ports@sources.redhat.com
Subject: Re: glibc-ports-2.12.1 tarball
Date: Tue, 16 Nov 2010 23:19:00 -0000 [thread overview]
Message-ID: <E1PIUBn-0000qV-Bg@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTim64ZVB3nfpRLkPsbsMFbvFo+Mev=3WQ=DSnatF@mail.gmail.com> (carlos@systemhalted.org)
If the tarball is based on the tag glibc-2.12.1 made on August 4th
by Joseph Myers, then please upload. My apologies for not replying
sooner.
There should be a tarball somewhere near you when you read
this. The following was used to generate, and upload:
git archive --prefix=glibc-ports-2.12.1/ glibc-2.12.1 > glibc-ports-2.12.1.tar
tar xf glibc-ports-2.12.1.tar
rm glibc-ports-2.12.1.tar
find glibc-ports-2.12.1 -name configure -print | xargs touch
tar -cf glibc-ports-2.12.1.tar glibc-ports-2.12.1
gzip -9c glibc-ports-2.12.1.tar > glibc-ports-2.12.1.tar.gz
bzip2 -9c glibc-ports-2.12.1.tar > glibc-ports-2.12.1.tar.bz2
~/gnulib/build-aux/gnuupload --to ftp.gnu.org:glibc \
--to amszmidt@sources.redhat.com:~ftp/pub/glibc/releases \
glibc-ports-2.12.1.tar.gz glibc-ports-2.12.1.tar.bz2
I'll send a small patch for the Makefile to handle this better, it
still assumes CVS.
The community needs a global ports maintainer to step-up and commit to
organizing all of the activities required for the community to
function.
I can help, but I do not have time to organise.
prev parent reply other threads:[~2010-11-16 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 22:20 Lluís Batlle i Rossell
2010-11-02 7:42 ` Marko Lindqvist
2010-11-02 15:06 ` Matt Turner
2010-11-02 21:58 ` Alfred M. Szmidt
2010-11-14 21:09 ` Carlos O'Donell
2010-11-16 23:19 ` Alfred M. Szmidt [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=E1PIUBn-0000qV-Bg@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=carlos@systemhalted.org \
--cc=libc-ports@sources.redhat.com \
--cc=mattst88@gmail.com \
--cc=viriketo@gmail.com \
/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).