The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [OT] 'git pull' from Linus' tree doesn't work for me any more
Date: Thu, 21 Aug 2008 01:16:44 +0200	[thread overview]
Message-ID: <200808210116.44546.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.1.10.0808201557430.3487@nehalem.linux-foundation.org>

On Thursday, 21 of August 2008, Linus Torvalds wrote:
> 
> On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
> > 
> > Well, it hasn't been working for a couple of hours now ...
> 
> Hmm. I just tested it myself, and it worked fine for me to just update 
> another machine by pulling from git.kernel.org.
> 
> What version of git do you have? One thing that changed recently is that 
> at least some kernel.org git binaries got updated to 1.6.0, and if you 
> have a really ancient version of git (Debian 'stable' aka 'rubbish' ships 
> with something two years old), you'd better upgrade.
> 
> From the 1.6.0 announcement:
> 
>   GIT v1.6.0 Release Notes
>   ========================
>   
>   User visible changes
>   --------------------
>   
>   With the default Makefile settings, most of the programs are now
>   installed outside your $PATH, except for "git", "gitk" and
>   some server side programs that need to be accessible for technical
>   reasons.  Invoking a git subcommand as "git-xyzzy" from the command
>   line has been deprecated since early 2006 (and officially announced in
>   1.5.4 release notes); use of them from your scripts after adding
>   output from "git --exec-path" to the $PATH is still supported in this
>   release, but users are again strongly encouraged to adjust their
>   scripts to use "git xyzzy" form, as we will stop installing
>   "git-xyzzy" hardlinks for built-in commands in later releases.
>   
>   An earlier change to page "git status" output was overwhelmingly unpopular
>   and has been reverted.
>   
>   Source changes needed for porting to MinGW environment are now all in the
>   main git.git codebase.
>   
>   By default, packfiles created with this version uses delta-base-offset
>   encoding introduced in v1.4.4.  Pack idx files are using version 2 that
>   allows larger packs and added robustness thanks to its CRC checking,
>   introduced in v1.5.2 and v1.4.4.5.  If you want to keep your repositories
>   backwards compatible past these versions, set repack.useDeltaBaseOffset
>   to false or pack.indexVersion to 1, respectively.
>   
> and no, I am not at all interested in helping Debian continue to ship
> git versions almost two years old, and much inferior to modern versions. 
> So I'm not going to set the flag that makes it work with old gits.

I have 1.5.2.4 and it works now.

Thanks,
Rafael

  reply	other threads:[~2008-08-20 23:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 22:45 [OT] 'git pull' from Linus' tree doesn't work for me any more Rafael J. Wysocki
2008-08-20 22:51 ` Linus Torvalds
2008-08-20 22:58   ` Rafael J. Wysocki
2008-08-20 23:03     ` Justin P. Mattock
2008-08-20 23:06     ` H. Peter Anvin
2008-08-20 23:17       ` Rafael J. Wysocki
2008-08-20 23:07     ` Linus Torvalds
2008-08-20 23:16       ` Rafael J. Wysocki [this message]
2008-08-20 23:21       ` Justin P. Mattock

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=200808210116.44546.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --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