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

[PATCH v2 0/4] implement automatic submodule merge strategy when possible

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Jul 6, 2010, 19:34 UTC
Message-ID
<cover.1278444110.git.hvoigt@hvoigt.net>
Changes since the previous iteration:
 * Add missing option --ancestry-path to setup_revisions()
 * Drop unnecessary caching of submodule refs
 * Use buf.len instead of NUL-padding for path buffer in
   git_path_submodule()
 * Extend the testcases so they will check for the correct suggestion
   output in case of a failed merge.
 * cleanup of some comments
Heiko Voigt (4):
  add missing && to submodule-merge testcase
  teach ref iteration module about submodules
  extent setup_revisions() so it works with submodules
  implement automatic fast forward merge for submodules
 cache.h                    |    3 +
 merge-recursive.c          |    9 ++-
 path.c                     |   38 +++++++++++
 refs.c                     |  149 ++++++++++++++++++++++++++++++++---------
 refs.h                     |    8 ++
 revision.c                 |   32 +++++----
 revision.h                 |    1 +
 submodule.c                |  158 ++++++++++++++++++++++++++++++++++++++++++++
 submodule.h                |    2 +
 t/t7405-submodule-merge.sh |  129 ++++++++++++++++++++++++++++++++++--
 10 files changed, 473 insertions(+), 56 deletions(-)
-- 
1.7.2.rc1.217.g7dc0db.dirty
Next: Heiko Voigt
Message 1 of 11 in “implement automatic submodule merge strategy when possible”
  1. 0/4 implement automatic submodule merge strategy when possibleHeiko Voigt, Jul 6, 2010
  2. 1/4 add missing && to submodule-merge testcaseHeiko Voigt, Jul 6, 2010
  3. 2/4 teach ref iteration module about submodulesHeiko Voigt, Jul 6, 2010
  4. 3/4 extent setup_revisions() so it works with submodulesHeiko Voigt, Jul 6, 2010
  5. Junio C HamanoJul 7, 2010
  6. Heiko VoigtJul 7, 2010
  7. 4/4 implement automatic fast forward merge for submodulesHeiko Voigt, Jul 6, 2010
  8. Johan HerlandJul 6, 2010
  9. Heiko VoigtJul 7, 2010
  10. Junio C HamanoJul 8, 2010
  11. Johan HerlandJul 6, 2010

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.