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 13:28:00 -0400 [thread overview]
Message-ID: <42B84E20.7010100@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506210905560.2268@ppc970.osdl.org>
Linus Torvalds wrote:
> It's not quite your "switch", though, because it will always _write_ to
> the current HEAD, it won't be switching the current HEAD around to another
> branch. I almost think that behavkiour would be more useful, I'll think
> about how to do it sanely.
The reason I requested git-checkout-script is to make git-switch-tree
pretty much trivial. The new git-switch-tree will sit on top of
git-checkout-script, like
if $1
switch HEAD to refs/heads/$1
git-checkout-script
So, as created, git-checkout-script is a useful foundation for other
scripts.
As of right now, I only have two[1] scripts that are non-vanilla:
git-switch-tree: retarget .git/HEAD to refs/heads/$1
git-new-branch: cp refs/heads/master refs/heads/$1
With git-checkout-script, both of these are now trivial and obvious.
Jeff
[1] Actually I have a third, 'git-changes-script'. The only reason I
use this is that it supports the old BitKeeper syntax of
cd my-repo-2.6
git-changes-script -L ../linux-2.6
to obtain a list of changes that are _only_ present in my-repo-2.6, and
not in ../linux-2.6 repo. git-changes-script works with .git/HEAD at
the repo level, and knows nothing of branches (which is fine).
next prev parent reply other threads:[~2005-06-21 17:28 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
2005-06-21 17:06 ` Linus Torvalds
2005-06-21 17:28 ` Jeff Garzik [this message]
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=42B84E20.7010100@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.