From: Daniel Phillips <lkml@phunq.net>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tux3 report: New news for the new year
Date: Tue, 01 Jan 2013 05:28:04 -0800 [thread overview]
Message-ID: <1492866.3ugQ2fqrP0@mars> (raw)
In-Reply-To: <201301011406.19983.Martin@lichtvoll.de>
On Tuesday, January 01, 2013 02:06:19 PM Martin Steigerwald wrote:
> Sounds all good and nice and interesting to test, but where to grab the
> source?
>
> I found no obvious URL.
Hi Martin,
Sorry about that, I knew I forgot something:
git://github.com/OGAWAHirofumi/tux3.git
Warning: the recent work is on branch temp-atomic-commit and tends to get
refactored changeset-wise on a regular basis. This will be merged to master
pretty soon, and settle down there.
> http://tux3.org/source.html:
> merkaba:/tmp> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/daniel/linux-tux3.git Cloning
> into 'linux-tux3'...
> fatal: The remote end hung up unexpectedly
I need to do the right incantations to bring the kernel.org tree up again.
Tux3.org needs some loving. Volunteers welcome.
Regards,
Daniel
next prev parent reply other threads:[~2013-01-01 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 11:52 Tux3 report: New news for the new year Daniel Phillips
2013-01-01 13:06 ` Martin Steigerwald
2013-01-01 13:28 ` Daniel Phillips [this message]
2013-01-01 14:37 ` Martin Steigerwald
2013-01-01 21:49 ` Daniel Phillips
2013-01-02 6:58 ` Shentino
2013-01-02 6:58 ` Shentino
2013-01-02 11:03 ` Daniel Phillips
2013-01-02 9:45 ` Tero Roponen
2013-01-02 11:15 ` Daniel Phillips
2013-01-04 10:04 ` OGAWA Hirofumi
2013-01-05 9:35 ` Shentino
-- strict thread matches above, loose matches on Subject: below --
2013-01-01 10:55 Daniel Phillips
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=1492866.3ugQ2fqrP0@mars \
--to=lkml@phunq.net \
--cc=Martin@lichtvoll.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.