All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Münster" <pmlists@free.fr>
To: git@vger.kernel.org
Subject: Re: feature request: git svn dommit --preserve-timestamps
Date: Wed, 08 Jun 2016 20:31:12 +0200	[thread overview]
Message-ID: <874m93y1lb.fsf@free.fr> (raw)
In-Reply-To: 87a8iy6s4e.fsf@free.fr

On Mon, Jun 06 2016, Peter Münster wrote:

> It would be nice, if timestamps could be preserved when rewriting the
> git-log.
>
> 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).
>
> TIA for your attention and perhaps the implementation of such a feature.

Hi,

Or could someone please show me, where the timestamp is rewritten in the
code, so that I could change it and compile a local copy of git, that
fits my needs? Perhaps I could even create a patch, that implements
"--preserve-timestamps" and send it back.

I've already searched in git-svn.perl but without success... :(

TIA for any hints,
-- 
           Peter

      parent reply	other threads:[~2016-06-08 18:35 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
2016-06-11 11:43         ` Eric Wong
2016-06-12 10:23           ` Peter Münster
2016-06-08 18:31 ` Peter Münster [this message]

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=874m93y1lb.fsf@free.fr \
    --to=pmlists@free.fr \
    --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.