From: "Shawn O. Pearce" <spearce@spearce.org>
To: Poojan Wagh <poojanwagh@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Q: How to tag individual files
Date: Sun, 13 Jul 2008 05:35:37 +0000 [thread overview]
Message-ID: <20080713053537.GA32746@spearce.org> (raw)
In-Reply-To: <g5bvte$52j$1@ger.gmane.org>
Poojan Wagh <poojanwagh@gmail.com> wrote:
> The crash course at: http://git.or.cz/course/svn.html says:
>
>> You usually tag commits but if you want, you can tag files (or trees,
>> but that's a bit low-level) as well.
>
> I've done a bit of searching, and I can't for the life of me figure out
> how to tag an individual file. Help from the group would be much
> appreciated. Thanks.
You don't tag individual files. Git is snapshot based. You tag
the entire project at once.
The comment you quoted was talking about tagging a single listing of
blobs (a tree) or a single blob (stream of bytes). This can be handy
in rare cases. In the linux kernel for example the prior history
was stored by tagging the tree of that prior history, as there was
no git based history preceeding that snapshot, so there were no
commits to tag. In git.git Junio publishes his GnuPG public key
as a tagged blob, making it available to validate signed tag objects.
So you can't tag individual files. The comment is a bit misleading
and gets far too low-level for an otherwise high-level conversion
guide.
--
Shawn.
next prev parent reply other threads:[~2008-07-13 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 4:21 Q: How to tag individual files Poojan Wagh
2008-07-13 5:35 ` Shawn O. Pearce [this message]
2008-07-13 6:14 ` Poojan Wagh
2008-07-13 10:20 ` Petr Baudis
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=20080713053537.GA32746@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=poojanwagh@gmail.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 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).