git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sam McKelvie <sammck@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] submodule: Alllow staged changes for get_superproject_working_tree
Date: Thu, 27 Sep 2018 18:43:22 -0700	[thread overview]
Message-ID: <xmqqmus2e6rp.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <D09E2583-BD1D-4C56-9C19-6B1E97CEEDAA@gmail.com> (Sam McKelvie's message of "Thu, 27 Sep 2018 17:30:21 -0700")

Sam McKelvie <sammck@gmail.com> writes:

>>> Subject: Re: [PATCH] submodule: Alllow staged changes for get_superproject_working_tree
>> 
>> s/Alllow/allow/;
>> 
>
> Ok, no caps on first letter of subject.

Ah, that, too.  I meant to correct triple ell, though ;-)

When one reviewer says Reviewed-by: but you later found that the
patch was not good enough to deserve a redoing, feel free to redo
the patch and do not add the Reviewed-by: you got for the old one
to your second submission.  The difference between the one that was
reviewed and the one you updated invalidates the stale Reviewed-by:,
essentially.

Some reviewers explicitly state "With this and that nit corrected or
left as-is, the patch is Reviewed-by: me" to tell you that as long
as the difference between the version reviewed and the updated one
is limited within the named issues, you can add Reviewed-by: to your
rerolled patch.

In this case, I think the nits are pretty small and I do not mind
tweaking the version we are discussing on my end, without having you
to send an updated one.

Here is what I'd squash into your commit, with title corrected, if
you are OK with that plan.  In the meantime, I'll keep the following
as a separate patch on top when I merge your fix to 'pu'.

Thanks.

 t/t1500-rev-parse.sh | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/t/t1500-rev-parse.sh b/t/t1500-rev-parse.sh
index b774cafc5d..01abee533d 100755
--- a/t/t1500-rev-parse.sh
+++ b/t/t1500-rev-parse.sh
@@ -134,6 +134,7 @@ test_expect_success 'rev-parse --is-shallow-repository in non-shallow repo' '
 test_expect_success 'showing the superproject correctly' '
 	git rev-parse --show-superproject-working-tree >out &&
 	test_must_be_empty out &&
+
 	test_create_repo super &&
 	test_commit -C super test_commit &&
 	test_create_repo sub &&
@@ -142,20 +143,20 @@ test_expect_success 'showing the superproject correctly' '
 	echo $(pwd)/super >expect  &&
 	git -C super/dir/sub rev-parse --show-superproject-working-tree >out &&
 	test_cmp expect out &&
+
 	test_commit -C super submodule_add &&
 	git -C super checkout -b branch1 &&
 	git -C super/dir/sub checkout -b branch1 &&
 	test_commit -C super/dir/sub branch1_commit &&
 	git -C super add dir/sub &&
 	test_commit -C super branch1_commit &&
-	git -C super checkout master &&
-	git -C super checkout -b branch2 &&
-	git -C super/dir/sub checkout master &&
-	git -C super/dir/sub checkout -b branch2 &&
+	git -C super checkout -b branch2 master &&
+	git -C super/dir/sub checkout -b branch2 master &&
 	test_commit -C super/dir/sub branch2_commit &&
 	git -C super add dir/sub &&
 	test_commit -C super branch2_commit &&
 	test_must_fail git -C super merge branch1 &&
+
 	git -C super/dir/sub rev-parse --show-superproject-working-tree >out &&
 	test_cmp expect out
 '

  reply	other threads:[~2018-09-28  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 18:10 [PATCH] submodule: Alllow staged changes for get_superproject_working_tree Sam McKelvie
2018-09-27 19:42 ` Stefan Beller
2018-09-27 22:02 ` Junio C Hamano
2018-09-28  0:30   ` Sam McKelvie
2018-09-28  1:43     ` Junio C Hamano [this message]
2018-09-28  3:29       ` Sam McKelvie
2018-09-28 18:00         ` Junio C Hamano
2018-09-28 21:59           ` Sam McKelvie
2018-09-28 22:25             ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqmus2e6rp.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sammck@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).