Re: Is git mktag supposed to accept git cat-file input?
- From
Michael J Gruber <git@drmicha.warpmail.net>
- Date
- Oct 25, 2012, 08:34 UTC
- Message-ID
- <5088F9AB.8090203@drmicha.warpmail.net>
- In-Reply-To
- <CAM1C4Gn6tr_bxG1De+kZecpJ7kLg7_hOO7q-aa7HwFkr9od6_Q@mail.gmail.com>
Anand Kumria venit, vidit, dixit 25.10.2012 02:58:
> Ahh, unix time. Of course.
That's the only difference *at the time being*, but this is not guaranteed. Really, as Brandon says: "cat-file -p" is pretty printing for human readability (which could be improved), and "cat-file <type>" is the raw format which is the content being hashed to the sha1.
Show 38 quoted lines
> > Thanks Brandon. > > On 25 October 2012 01:18, Brandon Casey <drafnel@gmail.com> wrote: >> On Wed, Oct 24, 2012 at 4:39 PM, Anand Kumria <akumria@acm.org> wrote: >>> Hi, >>> >>> I am doing some experimenting with git-mktag, and was looking into the >>> format it expects on input. >>> >>> Should this sequence of commands work? >> >> Yes, with a slight tweak... >> >>> kalki:[/tmp/gittest]% git tag -m "tag-test" tag-test >>> kalki:[/tmp/gittest]% git cat-file -p e619 >> >> '-p' means pretty-print, i.e. produce a human-readable format. mktag >> supports the raw format. So you should invoke it like this: >> >> $ git cat-file tag e619 >> >> which should produce something like: >> >> object c0ae36fee730f7034b1f76c1490fe6f46f7ecad5 >> type commit >> tag tag-test >> tagger Anand Kumria <akumria@acm.org> 1351121552 +0100 >> >> tag-test >> >> and is the format expected by mktag. >> >> -Brandon >> > > >