public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24•org>
To: "Peter Münster" <pmlists@free•fr>
Cc: git@vger•kernel.org
Subject: Re: feature request: git svn dommit --preserve-timestamps
Date: Tue, 7 Jun 2016 00:09:02 +0000	[thread overview]
Message-ID: <20160607000902.GA4445@dcvr.yhbt.net> (raw)
In-Reply-To: <87a8iy6s4e.fsf@free.fr>

Peter Münster <pmlists@free•fr> wrote:
> It would be nice, if timestamps could be preserved when rewriting the
> git-log.

Unfortunately, last I checked (a long time ago!), explicitly
setting revprops might require SVN administrators to enable the
feature for the repo.

It's been a while and I'm not up-to-date with the latest SVN.
Maybe there's a newer/easier way you could give us details about :)

> Use case: I often make a dcommit after several days of development
> (20 or 30 commits), because
> - the users of the svn-server don't need it more often;
> - and for the dcommit I need a VPN-connection to a server, that is not
>   always available.
> 
> Today, after a dcommit, it's no more possible to match a special commit
> by time and date (for example the time of some email exchange).

For now, I suggest including the date in the message body itself
to record when it was written (perhaps using git-interpret-trailers
to enforce, although I'm not familiar with that, either).

  reply	other threads:[~2016-06-07  0:09 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 [this message]
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
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=20160607000902.GA4445@dcvr.yhbt.net \
    --to=e@80x24$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=pmlists@free$(echo .)fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox