From: Stefan Monnier <monnier@iro•umontreal.ca>
To: git@vger•kernel.org
Subject: Re: fast-import fails in read-only tree
Date: Sat, 30 Jan 2016 08:56:48 -0500 [thread overview]
Message-ID: <jwvtwlv18jw.fsf-monnier+gmane.comp.version-control.git@gnu.org> (raw)
In-Reply-To: 20160130051340.GA1677@sigill.intra.peff.net
> You can use custom cat-file formatting to output your "name" strings as
> part of the same field. IOW, something like:
[...]
> If you're really going to do a lot of interactive back-and-forth access
> of objects, though, I think you want to set up pipes to cat-file.
OMG, I didn't realize that cat-file doesn't buffer its output so it can
be read&write to/from the same process. And the "%(rest)" thingy takes
care of the rest of my needs, indeed.
Thanks!
> It's a little tedious to allocate fifos, but something like:
That's not a problem.
> One feature I do think would be useful (and almost implemented when I
> added --batch-check=<format>) is a formatter for the object content,
> with a pretty modifier. I.e., it would be nice to do:
>
> echo $some_tree |
> git cat-file --batch-check="%(objectsize:pretty) %(contents:pretty)"
>
> to work as the rough equivalent of "git cat-file -p" (but here you could
> feed multiple trees and get multiple answers).
Yes, that would be a good improvement,
Stefan
prev parent reply other threads:[~2016-01-30 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 22:17 fast-import fails in read-only tree Stefan Monnier
2016-01-29 6:08 ` Jeff King
2016-01-29 14:28 ` Stefan Monnier
2016-01-30 5:13 ` Jeff King
2016-01-30 9:05 ` Andreas Schwab
2016-01-30 13:56 ` Stefan Monnier [this message]
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=jwvtwlv18jw.fsf-monnier+gmane.comp.version-control.git@gnu.org \
--to=monnier@iro$(echo .)umontreal.ca \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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