Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 23:16:10 +1000	[thread overview]
Message-ID: <20080704231610.98118766.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080704114648.13374869@lxorguk.ukuu.org.uk>

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

On Fri, 4 Jul 2008 11:46:48 +0100 Alan Cox <alan@lxorguk.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@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

  reply	other threads:[~2008-07-04 13:16 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
2008-07-04 13:16   ` Stephen Rothwell [this message]
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=20080704231610.98118766.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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