From: Valdis.Kletnieks@vt.edu
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 5
Date: Wed, 05 Oct 2011 09:17:47 -0400 [thread overview]
Message-ID: <29826.1317820667@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 05 Oct 2011 23:36:25 +1100." <20111005233625.a5a6e83e53a338c7b4e205ff@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Wed, 05 Oct 2011 23:36:25 +1100, Stephen Rothwell said:
> Yeah, linux-next is not back on git.kernel.org yet. See the note at the
> top of the email you quoted above:
>
> "The linux-next tree is now available from
> git://github.com/sfrothwell/linux-next.git as a temporary measure while
> the kernel.org servers are unavailable."
-ENOCAFFEINE - I saw the git://git.kernel.org and thought "Oh good, Stephen is
back up and running on kernel.org again".
The spectacularly unhelpful behavior of git didn't help matters any.
If it had printed out "no such tree here" or similar rather than just
hanging up, I'd probably have gone back and re-read the mail...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-10-05 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 8:37 linux-next: Tree for Oct 5 Stephen Rothwell
2011-10-05 12:09 ` Valdis.Kletnieks
2011-10-05 12:36 ` Stephen Rothwell
2011-10-05 13:17 ` Valdis.Kletnieks [this message]
2012-10-05 4:54 Stephen Rothwell
2016-10-05 5:14 Stephen Rothwell
2018-10-05 6:39 Stephen Rothwell
2018-10-05 13:48 ` Guenter Roeck
2021-10-05 8:06 Stephen Rothwell
2022-10-05 7:26 Stephen Rothwell
2023-10-05 3:45 Stephen Rothwell
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=29826.1317820667@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).