public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Dave Airlie <airlied@linux.ie>, linux-kernel@vger.kernel.org
Subject: Re: git-pull-script on my linus tree fails..
Date: Tue, 21 Jun 2005 11:56:44 -0400	[thread overview]
Message-ID: <42B838BC.8090601@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506210837020.2268@ppc970.osdl.org>

Linus Torvalds wrote:
> I guess I can make the "git pull" script do that automatically (some other
> scripts do, like "git commit", which also depends on having an up-to-date
> index).

Slight tangent...  it would be nice if you would write a 2-line 
git-checkout-script, which provides the modern version of

	git-read-tree -m HEAD && git-checkout-cache -q -f -u -a

Note that I do depend on this command blowing away working dir changes, 
but maybe you would want that to be a separate arg.

Then you could add a "-u" arg, or somesuch, to the situations like git 
pull that want an up-to-date index.

	Jeff



  reply	other threads:[~2005-06-21 15:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 12:07 git-pull-script on my linus tree fails Dave Airlie
2005-06-21 15:39 ` Linus Torvalds
2005-06-21 15:56   ` Jeff Garzik [this message]
2005-06-21 17:06     ` Linus Torvalds
2005-06-21 17:28       ` Jeff Garzik
2005-06-21 17:42         ` Linus Torvalds
2005-06-21 17:53           ` Jeff Garzik
2005-06-21 18:08             ` Linus Torvalds
2005-06-21 18:17               ` Jeff Garzik
2005-06-21 18:25                 ` Linus Torvalds
2005-06-21 23:52                   ` Jeff Garzik
2005-06-21 23:54                     ` Jeff Garzik
2005-06-22  0:13                       ` Linus Torvalds
2005-06-22  0:46                         ` Jeff Garzik
2005-06-22  1:18                           ` Linus Torvalds
2005-06-22  5:51                             ` Jeff Garzik

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=42B838BC.8090601@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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