From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: StGIT refreshes all added files - limitation of git-write-tree?
Date: Wed, 15 Feb 2006 04:06:17 -0500 [thread overview]
Message-ID: <1139994377.5796.30.camel@dv> (raw)
In-Reply-To: <7vacctnnx4.fsf@assigned-by-dhcp.cox.net>
On Tue, 2006-02-14 at 22:20 -0800, Junio C Hamano wrote:
> Pavel Roskin <proski@gnu.org> writes:
>
> > Or maybe git-write-tree and other utilities could be changed to work on
> > a copy of the index file? I would prefer not to move the
> > actual .git/index away, but to make a copy for the current "stg refresh"
> > operation.
>
> There is no need to change the core side.
>
> GIT_INDEX_FILE=temporary-index git-write-tree
>
> would do the job. See the current round of git-commit and how
> it handles "git commit --only these files" case.
Thank you! It's comforting to know that the issue is not unique to
StGIT.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-02-15 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 4:42 StGIT refreshes all added files - limitation of git-write-tree? Pavel Roskin
2006-02-15 6:20 ` Junio C Hamano
2006-02-15 9:06 ` Pavel Roskin [this message]
2006-02-15 6:28 ` Shawn Pearce
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=1139994377.5796.30.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.