git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCHv2 0/3] Reroll of sb/submodule-merge-in-merge-recursive

From
Stefan Beller <sbeller@google.com>
Date
May 15, 2018, 20:00 UTC
Message-ID
<20180515200030.88731-1-sbeller@google.com>

This rerolls the two commits found at [1] with the feedback of Eliah and puts Leifs patch[2] on top, that I edited according to Eliahs feedback, but kept Leifs ownership.

This has addressed all of Eliahs feedback AFAICT. You'll find a branch-diff below[3], which lacks the new patch of Leif in that series, but is part of the reroll?

Leif, what do you think?

Thanks, Stefan

[1] https://public-inbox.org/git/20180510211917.138518-1-sbeller@google.com/ [2] https://public-inbox.org/git/20180514205737.21313-2-leif.middelschulte@gmail.com/ [3] git branch-diff origin/master..origin/sb/submodule-merge-in-merge-recursive origin/master..HEAD >>0000-cover-letter.patch

Leif Middelschulte (1):
  Inform about fast-forwarding of submodules during merge
Stefan Beller (2):
  submodule.c: move submodule merging to merge-recursive.c
  merge-recursive: i18n submodule merge output and respect verbosity
 merge-recursive.c | 185 +++++++++++++++++++++++++++++++++++++++++++++-
 submodule.c       | 168 +----------------------------------------
 submodule.h       |   6 +-
 3 files changed, 186 insertions(+), 173 deletions(-)
-- 
2.17.0.582.gccdcbd54c44.dirty



1:  e022c7976ae ! 1:  3b638ccac64 submodule.c: move submodule merging to merge-recursive.c
    @@ -20,7 +20,6 @@
         This commit is best viewed with --color-moved.
     
         Signed-off-by: Stefan Beller <sbeller@google.com>
    -    Signed-off-by: Junio C Hamano <gitster@pobox.com>
     
     diff --git a/merge-recursive.c b/merge-recursive.c
     --- a/merge-recursive.c
2:  2c02ece7e01 ! 2:  eb43110df9d merge-recursive: i18n submodule merge output and respect verbosity
    @@ -7,7 +7,6 @@
         internationalisation as well as the verbosity setting.
     
         Signed-off-by: Stefan Beller <sbeller@google.com>
    -    Signed-off-by: Junio C Hamano <gitster@pobox.com>
     
     diff --git a/merge-recursive.c b/merge-recursive.c
     --- a/merge-recursive.c
    @@ -73,10 +72,10 @@
     -		fprintf(stderr, "Found a possible merge resolution "
     -				"for the submodule:\n");
     +		output(o, 1, _("Failed to merge submodule %s (not fast-forward)"), path);
    -+		output(o, 1, _("Found a possible merge resolution for the submodule:\n"));
    ++		output(o, 2, _("Found a possible merge resolution for the submodule:\n"));
      		print_commit((struct commit *) merges.objects[0].item);
     -		fprintf(stderr,
    -+		output(o, 1, _(
    ++		output(o, 2, _(
      			"If this is correct simply add it to the index "
      			"for example\n"
      			"by using:\n\n"
-:  ----------- > 3:  4a3bc435023 Inform about fast-forwarding of submodules during merge
Next: Stefan Beller
Message 1 of 19 in “[PATCHv2 0/3] Reroll of sb/submodule-merge-in-merge-recursive”
  1. Stefan BellerMay 15, 2018
  2. git-submodule.sh: try harder to fetch a submoduleStefan Beller, May 15, 2018
  3. 2/3 merge-recursive: i18n submodule merge output and respect verbosityStefan Beller, May 15, 2018
  4. Junio C HamanoMay 16, 2018
  5. 3/3 Inform about fast-forwarding of submodules during mergeStefan Beller, May 15, 2018
  6. Elijah NewrenMay 16, 2018
  7. Junio C HamanoMay 16, 2018
  8. Junio C HamanoMay 16, 2018
  9. 0/1 merge-recursive: give notice when submodule commit gets fast-forwardedLeif Middelschulte, Jun 4, 2018
  10. 1/1 merge-recursive: give notice when submodule commit gets fast-forwardedLeif Middelschulte, Jun 4, 2018
  11. Elijah NewrenJun 7, 2018
  12. merge-submodule: reduce output verbosityLeif Middelschulte, Jun 11, 2018
  13. Junio C HamanoJun 11, 2018
  14. Leif MiddelschulteJun 11, 2018
  15. grep: handle corrupt index files earlyStefan Beller, May 15, 2018
  16. 1/3 submodule.c: move submodule merging to merge-recursive.cStefan Beller, May 15, 2018
  17. Stefan BellerMay 15, 2018
  18. Leif MiddelschulteMay 15, 2018
  19. Stefan BellerMay 15, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.