Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Allow updating the index from a pipe
Date: Fri, 09 Dec 2005 23:06:37 -0800	[thread overview]
Message-ID: <7vbqzpxwg2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512100145500.25300@iabervon.org> (Daniel Barkalow's message of "Sat, 10 Dec 2005 01:57:05 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> In order to allow the index to be modified in simple ways without
> having a working tree, this adds an option to git-update-index which
> updates a single path with a mode of 100644 and reads the content from
> stdin.

I wonder ...

Could you do this with existing hash-object with update-index
--cache-info (or --index-info) please?  If you do not want a
temporary file and prefer piping contents into a command,
extending hash-object would be preferable.

  reply	other threads:[~2005-12-10  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10  6:57 [PATCH] Allow updating the index from a pipe Daniel Barkalow
2005-12-10  7:06 ` Junio C Hamano [this message]
2005-12-10  7: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=7vbqzpxwg2.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