From: Piotr Hosowicz <piotr@hosowicz.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Nexy <linux-next@vger.kernel.org>
Subject: Re: Why is next changing constantly?
Date: Mon, 26 Jul 2010 11:28:48 +0200 [thread overview]
Message-ID: <4C4D5550.9010607@example.com> (raw)
In-Reply-To: <20100726192525.4cca7d52.sfr@canb.auug.org.au>
On 26.07.2010 11:25, Stephen Rothwell wrote:
> Hi Piotr,
>
> On Mon, 26 Jul 2010 11:11:34 +0200 Piotr Hosowicz<piotr@hosowicz.com> wrote:
>>
>> I see linux-next row at kernel.org constatnly changing between 24 July
>> and todau 26 July. Why is that?
>
> My guess would be that some of the git.kernel.org mirrors are out of date.
Which is the main one? I have a script sensing me an email about new
versions and now it is flooding my inbox, I think I should use the main
server.
Regards,
Piotr Hosowicz
--
TV: "Gruchała jest taka, że cieszy się z każdego pchnięcia."
NP: Patrick O'Hearn - Magnificent River
NB: 2.6.35-rc6-git1
next prev parent reply other threads:[~2010-07-26 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 9:11 Why is next changing constantly? Piotr Hosowicz
2010-07-26 9:25 ` Stephen Rothwell
2010-07-26 9:28 ` Piotr Hosowicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-26 9:19 Piotr Hosowicz
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=4C4D5550.9010607@example.com \
--to=piotr@hosowicz.com \
--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 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.