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

Re: git-svn rebase screwing up commit messages

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 28, 2007, 12:14 UTC
Message-ID
<7v8x90sp25.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<724DFB31-0471-4A5E-95DF-F5F74876AC77@lrde.epita.fr>
Benoit SIGOURE <tsuna@lrde.epita.fr> writes:
> git version 1.5.2.3 over here, I've googled and searched in the ML
> archives but did not find this:  when I git-svn rebase, my commits in
> Git (that are temporarily removed and then re-applied) get their
> commit message flattened on a single line...

Do you mean by "my commits in Git" a commit you created with git in your git repository?

Previous: Benoit SIGOURENext: Sean
Message 2 of 18 in “git-svn rebase screwing up commit messages”
  1. Benoit SIGOUREJul 28, 2007
  2. Junio C HamanoJul 28, 2007
  3. SeanJul 28, 2007
  4. Junio C HamanoJul 28, 2007
  5. SeanJul 28, 2007
  6. Junio C HamanoJul 28, 2007
  7. SeanJul 28, 2007
  8. Junio C HamanoJul 28, 2007
  9. Junio C HamanoJul 29, 2007
  10. 1/3 log_ref_write() -- do not chomp reflog message at the first LFJunio C Hamano, Jul 29, 2007
  11. Johannes SchindelinJul 29, 2007
  12. Junio C HamanoJul 29, 2007
  13. Johannes SchindelinJul 29, 2007
  14. 2/3 symbolic-ref, update-ref: do not refuse reflog message with LFJunio C Hamano, Jul 29, 2007
  15. 3/3 rebase: try not to munge commit log messageJunio C Hamano, Jul 29, 2007
  16. Jakub NarebskiJul 28, 2007
  17. Robin RosenbergJul 28, 2007
  18. Benoit SIGOUREJul 28, 2007

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.