From: karthik nayak <karthik.188@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: [PATCH v9 0/5] cat-file: teach cat-file a '--allow-unkown-type' option
Date: Wed, 29 Apr 2015 18:20:31 +0530 [thread overview]
Message-ID: <5540D397.8020104@gmail.com> (raw)
The last iteration of the patch can be seen :
http://thread.gmane.org/gmane.comp.version-control.git/267213
Changes since last version:
sha1_file:
* eliminate "struct strbuf typename = STRBUF_INIT" in
"parse_sha1_header_extended()"
* make "unpack_sha1_header_to_strbuf()" work automagically. Now it
unpacks first 32 bytes and checks if the header is unpacked before
moving to a strbuf.
* remove unnecessary if condition for "strbuf_release()" .
cat-file:
* change the option name from "--literally" to "--allow-unkown-type".
* make the options mutually exclusive.
* clean up '-s' option.
t1006:
* use echo_without_newline() and added quotes.
next reply other threads:[~2015-04-29 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 12:50 karthik nayak [this message]
2015-04-29 12:52 ` [PATCH v9 1/5] sha1_file: support reading from a loose object of unknown type Karthik Nayak
2015-04-29 14:49 ` Junio C Hamano
2015-04-29 17:50 ` karthik nayak
2015-04-29 19:35 ` Junio C Hamano
2015-04-30 4:40 ` karthik nayak
2015-04-29 12:52 ` [PATCH v9 2/5] cat-file: make the options mutually exclusive Karthik Nayak
2015-04-29 12:53 ` [PATCH v9 3/5] cat-file: teach cat-file a '--allow-unknown-type' option Karthik Nayak
2015-04-29 14:52 ` Junio C Hamano
2015-04-29 17:43 ` karthik nayak
2015-04-29 14:53 ` Phil Hord
2015-04-29 17:44 ` karthik nayak
2015-04-29 19:38 ` Junio C Hamano
2015-04-29 12:54 ` [PATCH v9 5/5] t1006: add tests for git cat-file --allow-unkown-type Karthik Nayak
2015-04-29 21:16 ` Eric Sunshine
2015-04-29 12:56 ` [PATCH v9 4/5] cat-file: add documentation for '--allow-unkown-type' option Karthik Nayak
2015-04-29 21:13 ` Eric Sunshine
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=5540D397.8020104@gmail.com \
--to=karthik.188@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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).