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

[PATCH v4 0/4] Updated patch series for default upstream merge

From
Jared Hance <jaredhance@gmail.com>
Date
Feb 10, 2011, 23:40 UTC
Message-ID
<1297381209-6377-1-git-send-email-jaredhance@gmail.com>

This patch series allows for `git merge` to default to the upstream of the current branch.

This update adds fixes based on all of the style-feedback from the previous patch series; functionally it is equivalent (except for the first patch).

Should I have put the patch submitted by Jonathan Nieder in this series? I didn't place it in the tree but it should apply on top if it.

Jared Hance (4):
  merge: update the usage information to be more modern
  merge: introduce setup_merge_commit helper function
  merge: introduce per-branch-configuration helper function
  merge: add support for merging from upstream by default
 Documentation/config.txt |    6 +++
 builtin/merge.c          |   90 ++++++++++++++++++++++++++++++++--------------
 2 files changed, 69 insertions(+), 27 deletions(-)
-- 
1.7.4
Next: Jared Hance
Message 1 of 12 in “Updated patch series for default upstream merge”
  1. 0/4 Updated patch series for default upstream mergeJared Hance, Feb 10, 2011
  2. 1/4 merge: update the usage information to be more modernJared Hance, Feb 10, 2011
  3. 1/5 t5526: Fix wrong argument order in "git config"Jared Hance, Feb 10, 2011
  4. 2/4 merge: introduce setup_merge_commit helper functionJared Hance, Feb 10, 2011
  5. 2/5 merge: update the usage information to be more modernJared Hance, Feb 10, 2011
  6. 3/4 merge: introduce per-branch-configuration helper functionJared Hance, Feb 10, 2011
  7. 3/5 merge: introduce setup_merge_commit helper functionJared Hance, Feb 10, 2011
  8. 4/4 merge: add support for merging from upstream by defaultJared Hance, Feb 10, 2011
  9. Bert WesargFeb 11, 2011
  10. 4/5 merge: introduce per-branch-configuration helper functionJared Hance, Feb 10, 2011
  11. 5/5 merge: add support for merging from upstream by defaultJared Hance, Feb 10, 2011
  12. Jared HanceFeb 10, 2011

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.