public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki•fi>
To: Johannes Sixt <j.sixt@viscovery•net>
Cc: git@vger•kernel.org
Subject: Re: Making custom git-remove-tree command
Date: Thu, 04 Feb 2010 18:32:51 +0200	[thread overview]
Message-ID: <87tytxhsgc.fsf@mithlond.arda> (raw)
In-Reply-To: <4B6A9985.4050909@viscovery.net> (Johannes Sixt's message of "Thu, 04 Feb 2010 10:55:17 +0100")

* 2010-02-04 10:55 (+0100), Johannes Sixt wrote:

> I think you should be able to reduce all of this to just
>
> git read-tree --index-output=/tmp/empty.index -m -u \
> 	4b825dc642cb6eb9a060e54bf8d69288fbee4904 # empty tree
> rm -f /tmp/empty.index
>
> (with the usual caveats about temporary files).

Thanks, it works. It's also _much_ faster than my "git ls-tree" with
shell loop thing. It prints ugly error, though:

    fatal: unable to write new index file

Also, it doesn't leave any index output files around.

  reply	other threads:[~2010-02-04 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04  9:03 Making custom git-remove-tree command Teemu Likonen
2010-02-04  9:55 ` Johannes Sixt
2010-02-04 16:32   ` Teemu Likonen [this message]
2010-02-04 16:43     ` Johannes Sixt

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=87tytxhsgc.fsf@mithlond.arda \
    --to=tlikonen@iki$(echo .)fi \
    --cc=git@vger$(echo .)kernel.org \
    --cc=j.sixt@viscovery$(echo .)net \
    /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