linux-kernel - Re: linux-next: Tree for July 4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080704114648.13374869@lxorguk.ukuu.org.uk>
Date:	Fri, 4 Jul 2008 11:46:48 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for July 4

> 	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

> 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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/