public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk•ukuu.org.uk>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for July 4
Date: Fri, 4 Jul 2008 11:46:48 +0100	[thread overview]
Message-ID: <20080704114648.13374869@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20080704195529.7f56e768.sfr@canb.auug.org.au>

> 	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)

  reply	other threads:[~2008-07-04 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  9:55 linux-next: Tree for July 4 Stephen Rothwell
2008-07-04 10:46 ` Alan Cox [this message]
2008-07-04 13:16   ` Stephen Rothwell
2008-07-04 13:23     ` Alan Cox
2008-07-04 13:49       ` Stephen Rothwell
2008-07-04 13:34         ` Alan Cox
2008-07-04 13:53           ` Stephen Rothwell
2008-07-06 20:38 ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2011-07-04  7:09 Stephen Rothwell

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=20080704114648.13374869@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk$(echo .)ukuu.org.uk \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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