[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080704231610.98118766.sfr@canb.auug.org.au>
Date: Fri, 4 Jul 2008 23:16:10 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for July 4
On Fri, 4 Jul 2008 11:46:48 +0100 Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>
> > ttydev: fix pamc_zilog for tty pointer move
> > ttydev: sparc fix for tty move
> > ttydev: sparc32 fix for tty move
> > atmel_serial: Fix tty_port breakage
>
> Got these
Good. There are more broken drivers - check out
http://kisskb.ellerman.id.au/linux-next
> > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
> > are tracking the linux-next tree using git, you should not use "git pull"
> > to do so as that will try to merge the new linux-next release with the
> > old one. You should use "git fetch" as mentioned in the FAQ on the wiki
> > (see below).
>
> bash-3.2$ git fetch linux-next
> remote: error: refs/heads/history does not point to a valid object!
> remote: error: refs/heads/master does not point to a valid object!
> remote: error: refs/tags/next-20080704 does not point to a valid object!
>
> (on top of a clean current Linus git pull)
Were you using
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git or
http://www.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git ? The
git one works for me and the http does as well now that I have updated
the server info (though I neglected to try it before doing the update).
Thanks for the heads up.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists