All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Münster" <pmlists@free.fr>
To: Eric Wong <e@80x24.org>
Cc: git@vger.kernel.org
Subject: Re: feature request: git svn dommit --preserve-timestamps
Date: Sat, 11 Jun 2016 08:21:28 +0200	[thread overview]
Message-ID: <878tycmejb.fsf@free.fr> (raw)
In-Reply-To: <20160611013948.GA5793@dcvr.yhbt.net> (Eric Wong's message of "Sat, 11 Jun 2016 01:39:48 +0000")

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

  parent reply	other threads:[~2016-06-11  6:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 19:21 feature request: git svn dommit --preserve-timestamps Peter Münster
2016-06-07  0:09 ` Eric Wong
2016-06-07  5:44   ` Peter Münster
2016-06-11  1:39     ` Eric Wong
2016-06-11  2:12       ` Randall S. Becker
2016-06-11  6:21       ` Peter Münster [this message]
2016-06-11 11:43         ` Eric Wong
2016-06-12 10:23           ` Peter Münster
2016-06-08 18:31 ` Peter Münster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tycmejb.fsf@free.fr \
    --to=pmlists@free.fr \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.