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

[PATCH 0/1] git svn: use rebase --rebase-merges instead of preserve-merges

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
Nov 22, 2019, 22:59 UTC
Message-ID
<pull.295.git.1574463569.gitgitgadget@gmail.com>

By now, git rebase -r is on par with git rebase -p (or better), at least as far as git svn's usage is concerned. So let's use the former instead of the (deprecated) latter option.

Johannes Schindelin (1):
  git svn: stop using `rebase --preserve-merges`
 Documentation/git-svn.txt | 3 ++-
 git-svn.perl              | 9 +++++----
 2 files changed, 7 insertions(+), 5 deletions(-)
base-commit: d9f6f3b6195a0ca35642561e530798ad1469bd41
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-295%2Fdscho%2Fuse-rebase-r-in-git-svn-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-295/dscho/use-rebase-r-in-git-svn-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/295
-- 
gitgitgadget
Next: Johannes Schindelin via GitGitGadget
Message 1 of 3 in “git svn: use rebase --rebase-merges instead of preserve-merges”
  1. 0/1 git svn: use rebase --rebase-merges instead of preserve-mergesJohannes Schindelin via GitGitGadget, Nov 22, 2019
  2. 1/1 git svn: stop using `rebase --preserve-merges`Johannes Schindelin via GitGitGadget, Nov 22, 2019
  3. Eric WongNov 23, 2019

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.