public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: piotr@hosowicz•com
Cc: Linux Nexy <linux-next@vger•kernel.org>
Subject: Re: Why is next changing constantly?
Date: Mon, 26 Jul 2010 19:25:25 +1000	[thread overview]
Message-ID: <20100726192525.4cca7d52.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4C4D5146.1030109@example.com>

[-- Attachment #1: Type: text/plain, Size: 390 bytes --]

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.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2010-07-26  9:25 UTC|newest]

Thread overview: 3+ 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 [this message]
2010-07-26  9:28   ` 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=20100726192525.4cca7d52.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=piotr@hosowicz$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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