From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC] Two conceptually distinct commit commands
Date: Mon, 04 Dec 2006 22:19:55 +0100 [thread overview]
Message-ID: <el239s$e1i$1@sea.gmane.org> (raw)
In-Reply-To: 87bqmj2zit.wl%cworth@cworth.org
Carl Worth wrote:
> But what might be very interesting is a modified "git-apply --index"
> that would not fail in this case, but would instead do the following:
>
> 1. Apply the patch to the working tree
>
> 2. Apply the patch to the index
>
> And of course, if either fails then the entire apply operation fails,
> leaving no changes to working tree or to the index.
Or even new option to git-apply, namely --index-only, which would apply
patch to index only.
BTW. With git-apply we have three possibilities to apply patch to:
HEAD, index and working tree version, and three possibilities to
store result in: working tree only, working tree and index both,
and index only.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-04 21:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 19:08 [RFC] Two conceptually distinct commit commands Carl Worth
2006-12-04 20:10 ` Carl Worth
2006-12-04 21:19 ` Jakub Narebski [this message]
2006-12-05 2:36 ` Carl Worth
2006-12-05 0:52 ` Horst H. von Brand
2006-12-05 1:18 ` Carl Worth
2006-12-05 2:14 ` Horst H. von Brand
2006-12-05 2:32 ` Carl Worth
2006-12-05 1:19 ` Jakub Narebski
2006-12-05 3:51 ` Theodore Tso
2006-12-05 6:33 ` Junio C Hamano
2006-12-05 6:38 ` Carl Worth
2006-12-06 1:13 ` Junio C Hamano
2006-12-06 4:53 ` Carl Worth
2006-12-06 9:54 ` Commit order in git.git, was " Johannes Schindelin
2006-12-06 16:14 ` Carl Worth
2006-12-06 18:31 ` Junio C Hamano
2006-12-06 23:29 ` Carl Worth
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='el239s$e1i$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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 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.