From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Allow saving an object from a pipe
Date: Sat, 10 Dec 2005 18:59:13 -0800 [thread overview]
Message-ID: <7v64pwuyny.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.64.0512101724290.25300@iabervon.org
Daniel Barkalow <barkalow@iabervon.org> writes:
> In order to support getting data into git with scripts, this adds a
> --stdin option to git-hash-object, which will make it read from stdin.
Thanks, will apply.
To be honest, though, I am still debating myself about the merit
of not having to have a temporary file. Because we need the
size of the blob available before starting to hash (i.e. we
cannot say "atend"), index_pipe ends up keeping the whole blob
data in memory, which is not much better than the caller storing
it in a temporary file and driving the normal hash-object from
the command line anyway.
next prev parent reply other threads:[~2005-12-11 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 22:25 [PATCH] Allow saving an object from a pipe Daniel Barkalow
2005-12-11 2:59 ` Junio C Hamano [this message]
2005-12-12 17:12 ` Daniel Barkalow
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=7v64pwuyny.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--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