From: Marc Singer <elf@buici.com>
To: git@vger.kernel.org
Subject: How to get a directory filled with v2.6.11?
Date: Mon, 11 Jul 2005 22:03:47 -0700 [thread overview]
Message-ID: <20050712050347.GA10751@buici.com> (raw)
I switched to using the git version in source control.
Checkout/branching works great. :-)
But, this version of git doesn't let me do
# git checkout -f v2.6.11
error: Object 5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c is a tree, not a commit
Needed a single revision
which I suspect is protection added to prevent my special sort of
shenanigans. If I cannot perform the checkout anymore, is there
another way to fill a directory with the contents of that particular
tree?
What am I doing? I've got some updates against 2.6.11 orphaned in
another develpment directory. I could just upack a tar.bz2 file for
2.6.11, but git is more clever. I want to perform a diff against the
tagged v2.6.11 and my development tree.
next reply other threads:[~2005-07-12 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 5:03 Marc Singer [this message]
2005-07-12 6:18 ` How to get a directory filled with v2.6.11? Matthias Urlichs
2005-07-13 4:37 ` Linus Torvalds
2005-07-13 20:37 ` Junio C Hamano
2005-07-13 20:46 ` Linus Torvalds
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=20050712050347.GA10751@buici.com \
--to=elf@buici.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).