linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-next@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: SCSI trees moved back to kernel.org
Date: Wed, 12 Oct 2011 00:37:11 +0200	[thread overview]
Message-ID: <CA+icZUVC3CVgQqT_sR65MWzN=SWmgO4yaKAz4OJer9ch5jz=PQ@mail.gmail.com> (raw)
In-Reply-To: <1318351928.2992.19.camel@dabdike.int.hansenpartnership.com>

On Tue, Oct 11, 2011 at 6:52 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> On Thu, 2011-09-15 at 10:37 -0500, James Bottomley wrote:
>> I've relocated the scsi-rc-fixes and scsi-misc trees on to my own
>> infrastructure while master.kernel.org is down.  The locations are:
>>
>> git://bedivere.hansenpartnership.com/git/scsi-rc-fixes-2.6.git
>> git://bedivere.hansenpartnership.com/git/scsi-misc-2.6.git
>
> OK, all the trees are back in their usual locations on kernel.org,
> that's
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-post-merge-2.6.git
>

Die bad -2.6 suffix die :-)

- Sedat -

> I'll be shutting down git access on bedivere shortly.
>
> Thanks,
>
> james
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      parent reply	other threads:[~2011-10-11 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 15:37 Temporary location for some of the SCSI trees James Bottomley
2011-09-16  0:57 ` Stephen Rothwell
2011-10-11 16:52 ` SCSI trees moved back to kernel.org James Bottomley
2011-10-11 22:26   ` Stephen Rothwell
2011-10-11 22:35     ` James Bottomley
2011-10-11 22:44       ` Stephen Rothwell
2011-10-11 22:37   ` Sedat Dilek [this message]

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='CA+icZUVC3CVgQqT_sR65MWzN=SWmgO4yaKAz4OJer9ch5jz=PQ@mail.gmail.com' \
    --to=sedat.dilek@googlemail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --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).