linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-next@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: SCSI trees moved back to kernel.org
Date: Tue, 11 Oct 2011 17:35:16 -0500	[thread overview]
Message-ID: <1318372516.2992.32.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20111012092618.e35391f58873edb1cc0bb5cb@canb.auug.org.au>

On Wed, 2011-10-12 at 09:26 +1100, Stephen Rothwell wrote:
> Hi James,
> 
> On Tue, 11 Oct 2011 11:52:08 -0500 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> >
> > 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
> 
> OK, I have switched to use those.  However the last one gives:
> 
> fatal: Couldn't find remote ref refs/heads/merge-base

Um, sorry, fixed I think.  That's what comes of trying to create the
tree without actually having access to the old one.

James

  reply	other threads:[~2011-10-11 22:35 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 [this message]
2011-10-11 22:44       ` Stephen Rothwell
2011-10-11 22:37   ` Sedat Dilek

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=1318372516.2992.32.camel@dabdike.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@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).