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

Re: [PATCH v2 07/12] t4013: call git-merge instead of git-pull

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 8, 2015, 13:12 UTC
Message-ID
<cdd3a0b88d731a536735192317fff32b@www.dscho.org>
In-Reply-To
<CACRoPnTMgZBfeneMCZSJVowmSCGf2Ufpt-J461+w9Lh1aN-rhA@mail.gmail.com>
Hi Paul,
On 2015-05-07 18:55, Paul Tan wrote:
Show 19 quoted lines
> Hi Dscho,
> 
> On Fri, May 8, 2015 at 12:26 AM, Johannes Schindelin
> <johannes.schindelin@gmx.de> wrote:
>> Both this patch and 9/12 change `git pull` invocations to equivalent non-pull ones, but I wonder whether it would not be a better idea to leave them as-are, so that we can make sure that scripts out there that might use similar `git pull` invocations would be unaffected by the rewrite?
> 
> In the current state[1], I'm aiming for the git-pull rewrite patch
> series to break all git-pull tests in the first patch, and then
> subsequently make them pass again in later smaller patches by
> implementing back the old features. This will make reviewing the code
> much easier, as opposed to dumping a huge patch every single re-roll
> ;-).
> 
> For both patches and test suites, if the "setup" tests fail, the whole
> test suite fails. Given that the test suites are about testing the
> diff formatting options and submodules update implementation, which is
> mostly irrelevant to git-pull, I think it would be better if the test
> suite was not affected by the rewrite, especially since it only
> requires changing one line.
Ah, that makes sense. I just failed to understand what you were telling me.
Maybe it would be better to make that patch a part of the builtin pull instead, so that we do not forget to revert it with the commit that introduces support for `-s ours` in builtin pull?

Ciao, Dscho

Previous: Paul TanNext: Junio C Hamano
Message 24 of 49 in “Improve git-pull test coverage”
  1. 00/12 Improve git-pull test coveragePaul Tan, May 7, 2015
  2. 01/12 t5520: implement tests for no merge candidates casesPaul Tan, May 7, 2015
  3. Torsten BögershausenMay 7, 2015
  4. Junio C HamanoMay 7, 2015
  5. Paul TanMay 7, 2015
  6. Junio C HamanoMay 7, 2015
  7. Torsten BögershausenMay 7, 2015
  8. 02/12 t5520: test for failure if index has unresolved entriesPaul Tan, May 7, 2015
  9. Eric SunshineMay 7, 2015
  10. Paul TanMay 12, 2015
  11. 03/12 t5520: test work tree fast-forward when fetch updates headPaul Tan, May 7, 2015
  12. Stefan BellerMay 7, 2015
  13. Junio C HamanoMay 7, 2015
  14. Paul TanMay 7, 2015
  15. 04/12 t5520: test --rebase with multiple branchesPaul Tan, May 7, 2015
  16. 05/12 t5520: test --rebase failure on unborn branch with indexPaul Tan, May 7, 2015
  17. Stefan BellerMay 7, 2015
  18. Paul TanMay 7, 2015
  19. Eric SunshineMay 7, 2015
  20. 06/12 t5521: test --dry-run does not make any changesPaul Tan, May 7, 2015
  21. 07/12 t4013: call git-merge instead of git-pullPaul Tan, May 7, 2015
  22. Johannes SchindelinMay 7, 2015
  23. Paul TanMay 7, 2015
  24. Johannes SchindelinMay 8, 2015
  25. Junio C HamanoMay 7, 2015
  26. 08/12 t5520: ensure origin refs are updatedPaul Tan, May 7, 2015
  27. 09/12 t7406: use "git pull" instead of "git pull --rebase"Paul Tan, May 7, 2015
  28. Junio C HamanoMay 7, 2015
  29. Paul TanMay 7, 2015
  30. Junio C HamanoMay 7, 2015
  31. Paul TanMay 10, 2015
  32. 10/12 t5520: failing test for pull --all with no configured upstreamPaul Tan, May 7, 2015
  33. Junio C HamanoMay 7, 2015
  34. Paul TanMay 7, 2015
  35. Junio C HamanoMay 7, 2015
  36. Paul TanMay 9, 2015
  37. 11/12 t5524: test --log=1 limits shortlog lengthPaul Tan, May 7, 2015
  38. Johannes SchindelinMay 7, 2015
  39. Paul TanMay 7, 2015
  40. Johannes SixtMay 7, 2015
  41. Johannes SchindelinMay 8, 2015
  42. Thomas GummererMay 8, 2015
  43. Johannes SchindelinMay 8, 2015
  44. Johannes SixtMay 8, 2015
  45. Junio C HamanoMay 8, 2015
  46. Junio C HamanoMay 7, 2015
  47. 12/12 t5520: check reflog action in fast-forward mergePaul Tan, May 7, 2015
  48. Stefan BellerMay 7, 2015
  49. Junio C HamanoMay 7, 2015

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.