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: Re: [PATCH v6 3/4] reset: add a few tests for "git reset --merge"
Date: Sat, 2 Jan 2010 06:58:11 +0100 [thread overview]
Message-ID: <201001020658.12179.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7v7hs2o16j.fsf@alter.siamese.dyndns.org>
On vendredi 01 janvier 2010, Junio C Hamano wrote:
> Christian Couder <chriscool@tuxfamily.org> writes:
> > Commit 9e8eceab ("Add 'merge' mode to 'git reset'", 2008-12-01),
> > added the --merge option to git reset, but there were no test cases
> > for it.
> >
> > This was not a big problem because "git reset" was just forking and
> > execing "git read-tree", but this will change in a following patch.
> >
> > So let's add a few test cases to make sure that there will be no
> > regression.
> >
> > Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
>
> Looks good.
Thanks again.
> > +# The next test will test the following:
> > +#
> > +# working index HEAD target working index HEAD
> > +# ----------------------------------------------------
> > +# file1: C C C D --merge D D D
> > +# file2: C D D D --merge C D D
> > +test_expect_success 'reset --merge is ok with changes in file it does
> > not touch' ' + git reset --merge HEAD^ &&
> > + ! grep 4 file1 &&
> > + grep 4 file2 &&
> > + test "$(git rev-parse HEAD)" = "$(git rev-parse initial)" &&
> > + test -z "$(git diff --cached)"
> > +'
> > ...
> > +# The next test will test the following:
> > +#
> > +# working index HEAD target working index HEAD
> > +# ----------------------------------------------------
> > +# file1: C C C D --merge D D D
> > +# file2: C C D D --merge D D D
> > +test_expect_success 'reset --merge discards changes added to index
> > (2)' ' + git reset --hard second &&
> > + echo "line 4" >> file2 &&
> > + git add file2 &&
> > + git reset --merge HEAD^ &&
> > + ! grep 4 file2 &&
> > + test "$(git rev-parse HEAD)" = "$(git rev-parse initial)" &&
> > + test -z "$(git diff)" &&
> > + test -z "$(git diff --cached)"
> > +'
>
> These two seem to duplicate the same case for file1; is it necessary?
No. I think I just copied the previous test and added the "git add file2"
line.
> I am not pointing it out as something that needs to be removed; I am just
> puzzled and wondering if there is some interaction between the ways two
> paths are handled and the test is trying to check that (which I do not
> think is the case).
Best regards,
Christian.
next prev parent reply other threads:[~2010-01-02 5:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 5:54 [PATCH v6 0/4] "git reset --merge" related improvements Christian Couder
2009-12-30 5:54 ` [PATCH v6 1/4] reset: improve mixed reset error message when in a bare repo Christian Couder
2009-12-30 5:54 ` [PATCH v6 2/4] Documentation: reset: add some tables to describe the different options Christian Couder
2010-01-01 5:15 ` Junio C Hamano
2010-01-02 5:52 ` Christian Couder
2009-12-30 5:54 ` [PATCH v6 3/4] reset: add a few tests for "git reset --merge" Christian Couder
2010-01-01 5:15 ` Junio C Hamano
2010-01-02 5:58 ` Christian Couder [this message]
2009-12-30 5:54 ` [PATCH v6 4/4] reset: use "unpack_trees()" directly instead of "git read-tree" Christian Couder
2010-01-01 5:14 ` Junio C Hamano
2010-01-01 7:03 ` Junio C Hamano
2010-01-02 5:41 ` Christian Couder
2010-01-01 0:25 ` [PATCH v6 0/4] "git reset --merge" related improvements Linus Torvalds
2010-01-01 20:42 ` Junio C Hamano
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=201001020658.12179.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).