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

Re: feature request: git svn dommit --preserve-timestamps

From
PMPeter Münster <pmlists@free.fr>
Date
Jun 11, 2016, 06:21 UTC
Message-ID
<878tycmejb.fsf@free.fr>
In-Reply-To
<20160611013948.GA5793@dcvr.yhbt.net>
On Sat, Jun 11 2016, Eric Wong wrote:
> The git log after dcommit is tied to the SVN log,
> so git-svn can only reflect changes which appear in SVN.
You mean, it's impossible, to keep the original timestamps??
> 	Sidenote: The convention is reply-to-all on lists like
> 	this one which do not require subscription to post.
Ok, thanks.
> Unfortunately, you would have to care about svn log as long as
> SVN exists in your workflow and you need to interact with SVN
> users.

In my case, all development happens on Git, SVN is only some sort of copy. And when the original timestamps are lost, I've sometimes some real problems in finding a specific commit that matches another event.

> git svn tries hard to work transparently and as close to the
> behavior of the upstream SVN repo as possible.

That's why I suggest an option, for use cases as mine. Those, who prefer to keep the current behaviour just won't use it.

If someone could guide me through the code, I could modify it perhaps.
Thanks for your efforts,
-- 
           Peter
Previous: Randall S. BeckerNext: Eric Wong
Message 6 of 9 in “feature request: git svn dommit --preserve-timestamps”
  1. Peter MünsterJun 6, 2016
  2. Eric WongJun 7, 2016
  3. Peter MünsterJun 7, 2016
  4. Eric WongJun 11, 2016
  5. Randall S. BeckerJun 11, 2016
  6. Peter MünsterJun 11, 2016
  7. Eric WongJun 11, 2016
  8. Peter MünsterJun 12, 2016
  9. Peter MünsterJun 8, 2016

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.