From: karthik nayak <karthik.188@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: [PATCH v4 0/2] cat-file: add a '--literally' option
Date: Tue, 17 Mar 2015 10:43:18 +0530 [thread overview]
Message-ID: <5507B7EE.1070403@gmail.com> (raw)
Based on Junios and Erics suggestion I have made various
changes over the previous iteration of the patch[1].
Changes in this version :
* Add a object_info::typename to hold all the typenames.
* Add a wrapper around parse_sha1_header() to get type and
size of broken/corrupt objects without throwing an error
whenever the type is unknown.
* Also add an option for 'cat-file -s --literally'.
Thanks to Junio and Eric for their suggestions and guidance.
[1]http://article.gmane.org/gmane.comp.version-control.git/264853
next reply other threads:[~2015-03-17 5:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 5:13 karthik nayak [this message]
2015-03-17 5:16 ` [PATCH v4 1/2] cat-file: teach cat-file a '--literally' option Karthik Nayak
2015-03-17 6:51 ` Eric Sunshine
2015-03-17 13:59 ` Karthik Nayak
2015-03-17 5:16 ` [PATCH v4 2/2] sha1_file: refactor sha1_file.c to support 'cat-file --literally' Karthik Nayak
2015-03-17 20:10 ` Junio C Hamano
2015-03-18 19:35 ` karthik nayak
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=5507B7EE.1070403@gmail.com \
--to=karthik.188@gmail.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).