From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Stephan Beyer <s-beyer@gmx.net>,
Daniel Barkalow <barkalow@iabervon.org>,
Jakub Narebski <jnareb@gmail.com>,
Paolo Bonzini <bonzini@gnu.org>,
Johannes Sixt <j.sixt@viscovery.net>,
Stephen Boyd <bebarino@gmail.com>
Subject: [PATCH v5 0/7] "git reset --merge" related improvements
Date: Sat, 12 Dec 2009 05:32:51 +0100 [thread overview]
Message-ID: <20091212042042.3930.54783.chriscool@tuxfamily.org> (raw)
Another reroll with the following changes:
- the name of the new option is now "--keep" instead of "--keep-local-changes",
- the fill_tree_descriptor() function is used instead of adding a new
parse_and_init_tree_desc() function (thanks to Stephen Boyd),
- patch 1/7 was added to only accept soft reset when not in a working tree;
this makes the test suite pass,
- the commit message of patch 4/7 that adds the --keep option has been
improved; it talks more about the use case of this new option.
Christian Couder (6):
reset: do not accept a mixed reset in a .git dir
reset: add a few tests for "git reset --merge"
reset: add option "--keep" to "git reset"
reset: add test cases for "--keep" option
Documentation: reset: describe new "--keep" option
Documentation: reset: add some tables to describe the different
options
Stephan Beyer (1):
reset: use "unpack_trees()" directly instead of "git read-tree"
Documentation/git-reset.txt | 79 +++++++++++++++++++++-
builtin-reset.c | 74 +++++++++++++++-----
t/t7103-reset-bare.sh | 4 +-
t/t7110-reset-merge.sh | 156 +++++++++++++++++++++++++++++++++++++++++++
4 files changed, 292 insertions(+), 21 deletions(-)
create mode 100755 t/t7110-reset-merge.sh
next reply other threads:[~2009-12-12 4:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 4:32 Christian Couder [this message]
2009-12-12 4:32 ` [PATCH v5 1/7] reset: do not accept a mixed reset in a .git dir Christian Couder
2009-12-12 21:45 ` Junio C Hamano
2009-12-15 19:41 ` Christian Couder
2009-12-15 20:17 ` Junio C Hamano
2009-12-15 20:25 ` Junio C Hamano
2009-12-16 6:36 ` Christian Couder
2009-12-15 20:20 ` Junio C Hamano
2009-12-12 4:32 ` [PATCH v5 2/7] reset: add a few tests for "git reset --merge" Christian Couder
2009-12-12 23:30 ` Junio C Hamano
2009-12-12 4:32 ` [PATCH v5 3/7] reset: use "unpack_trees()" directly instead of "git read-tree" Christian Couder
2009-12-12 21:46 ` Junio C Hamano
2009-12-12 4:32 ` [PATCH v5 4/7] reset: add option "--keep" to "git reset" Christian Couder
2009-12-12 21:46 ` Junio C Hamano
2009-12-30 5:47 ` Christian Couder
2009-12-12 4:32 ` [PATCH v5 5/7] reset: add test cases for "--keep" option Christian Couder
2009-12-12 4:32 ` [PATCH v5 6/7] Documentation: reset: describe new " Christian Couder
2009-12-12 4:32 ` [PATCH v5 7/7] Documentation: reset: add some tables to describe the different options Christian Couder
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=20091212042042.3930.54783.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=bebarino@gmail.com \
--cc=bonzini@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=jnareb@gmail.com \
--cc=s-beyer@gmx.net \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).