From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org
Subject: util-linux repository back on kernel.org
Date: Mon, 7 Nov 2011 22:49:45 +0100 [thread overview]
Message-ID: <20111107214944.GD3322@nb.net.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
The original upstream code repository is back:
http://git.kernel.org/?p=utils/util-linux/util-linux.git
It seems that github web interface is very useful for some users and
reviewers, so I'm going to continue to push to the github as well as
to kernel.org. The github repository will be our backup.
git-repository: http://git.kernel.org/?p=utils/util-linux/util-linux.git (primary)
https://github.com/karelzak/util-linux (backup)
mailing-list: util-linux@vger.kernel.org
web-page: http://en.wikipedia.org/wiki/Util-linux
temporary FTP: ftp://ftp.infradead.org/pub/util-linux/
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2011-11-07 21:49 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=20111107214944.GD3322@nb.net.home \
--to=kzak@redhat.com \
--cc=util-linux@vger.kernel.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 NNTP newsgroup(s).