linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Marek <mmarek@suse.cz>,
	mark.asselstine@windriver.com, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild rc fixes for v3.6
Date: Thu, 6 Sep 2012 15:19:51 +1000	[thread overview]
Message-ID: <20120906151951.8c30cb06fcb20412910006d2@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFzBsKBmVMRiJ8yuML_QVQbfa2ZqHU_fh3_wS3YhLTv9fw@mail.gmail.com>

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

Hi Linus,

On Wed, 5 Sep 2012 20:32:00 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Mon, Sep 3, 2012 at 12:18 PM, Michal Marek <mmarek@suse.cz> wrote:
> >
> > The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
> >
> >   Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)
> >
> > are available in the git repository at:
> >   git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6.git ..BRANCH.NOT.VERIFIED..
> 
> There's something wrong with that repo
> 
>  "fatal: Could not read from remote repository.
> 
>   Please make sure you have the correct access rights
>   and the repository exists."
> 
> plus that BRANCH.NOT.VERIFIED thing looks bad too (and is probably related).

The kbuild-current tree in linux-next is

git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git rc-fixes

and it has those 2 commits in it.  So script update needed, I guess.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

  reply	other threads:[~2012-09-06  5:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03 19:18 [GIT] kbuild rc fixes for v3.6 Michal Marek
2012-09-06  3:32 ` Linus Torvalds
2012-09-06  5:19   ` Stephen Rothwell [this message]
2012-09-06 10:33     ` Michal Marek

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=20120906151951.8c30cb06fcb20412910006d2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.asselstine@windriver.com \
    --cc=mmarek@suse.cz \
    --cc=torvalds@linux-foundation.org \
    /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).