From: Greg KH <greg@kroah.com>
To: Paul Jackson <pj@sgi.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
pasky@ucw.cz, git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-pasky-0.7
Date: Sat, 23 Apr 2005 22:11:30 -0700 [thread overview]
Message-ID: <20050424051130.GA25332@kroah.com> (raw)
In-Reply-To: <20050423220236.26f834ee.pj@sgi.com>
On Sat, Apr 23, 2005 at 10:02:36PM -0700, Paul Jackson wrote:
> The winning solution via private email:
>
> mkdir linux
> cd linux
> git init rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>
> Another email was missing the 'scm' term.
>
> I still don't see how to get to the official 2.6.12-rc3:
>
> a2755a80f40e5794ddc20e00f781af9d6320fafb
From your "linux" directory do:
cd ..
mkdir 2.6.12-rc3
cd 2.6.12-rc3
mkdir .git
cp -rl ../linux/.git/object .git/objects
TREE_HEAD=`cat-file commit a2755a80f40e5794ddc20e00f781af9d6320fafb | head -n 1 | cut -f 2 -d " "`
echo "$TREE_HEAD" > .git/HEAD
read-tree $TREE_HEAD
checkout-cache -a
update-cache --refresh
And you should have a 2.6.12-rc3 tree, all ready to commit new changes
into.
Or at least that's how my wrapper scripts do it, I haven't converted
them over to the "easier" git-pasky commands yet :)
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-24 5:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 0:59 [ANNOUNCE] git-pasky-0.7 Petr Baudis
2005-04-24 1:26 ` Martin Schlemmer
2005-04-24 3:45 ` Linus Torvalds
2005-04-24 9:50 ` Martin Schlemmer
2005-04-24 3:58 ` Paul Jackson
2005-04-24 4:17 ` James Purser
2005-04-24 4:35 ` Paul Jackson
2005-04-24 4:32 ` Daniel Barkalow
2005-04-24 4:50 ` Paul Jackson
2005-04-24 4:58 ` James Purser
2005-04-24 5:02 ` Paul Jackson
2005-04-24 5:11 ` Greg KH [this message]
2005-04-24 5:12 ` Daniel Barkalow
2005-04-24 10:35 ` Martin Schlemmer
2005-04-24 7:14 ` Petr Baudis
2005-04-24 7:20 ` Paul Jackson
2005-04-24 10:52 ` Junio C Hamano
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=20050424051130.GA25332@kroah.com \
--to=greg@kroah.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=pj@sgi.com \
/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.