From: Michael Haggerty <mhagger@alum.mit.edu>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Ramkumar Ramachandra" <artagnon@gmail.com>,
"Joe Corneli" <holtzermann17@gmail.com>,
git@vger.kernel.org, "Love Hörnquist Åstrand" <lha@kth.se>
Subject: Re: working with a large repository and git svn
Date: Fri, 14 Jan 2011 10:23:59 +0100 [thread overview]
Message-ID: <4D30162F.5060408@alum.mit.edu> (raw)
In-Reply-To: <20110114082931.GC11343@burratino>
On 01/14/2011 09:29 AM, Jonathan Nieder wrote:
> . Is svn okay with non-monotonic dates? (If not, then the committer
> date would need to be used.)
Subversion can tolerate non-monotonic dates with one caveat: it breaks
the find-revision-by-date feature (e.g., "svn update -r '{2010-12-25}'")
for the time intervals with non-monotonic dates. This is a seldom-used
feature and therefore its sacrifice is often accepted, for example when
the history of the Subversion project itself was migrated into the
Apache project's Subversion repository.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-01-14 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 1:27 working with a large repository and git svn Joe Corneli
2011-01-12 15:30 ` Wesley J. Landaker
2011-01-13 0:54 ` Joe Corneli
2011-01-13 3:23 ` Jonathan Nieder
2011-01-14 7:43 ` Joe Corneli
2011-01-14 8:05 ` Ramkumar Ramachandra
2011-01-14 8:29 ` Jonathan Nieder
2011-01-14 9:23 ` Michael Haggerty [this message]
[not found] ` <F0299861-B36C-459C-972E-856212A92615@kth.se>
2011-01-14 10:16 ` [PATCH] Optionally parse author information Ramkumar Ramachandra
2011-01-16 2:17 ` Joe Corneli
2011-01-16 2:57 ` Jonathan Nieder
2011-01-16 3:32 ` Ramkumar Ramachandra
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=4D30162F.5060408@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=holtzermann17@gmail.com \
--cc=jrnieder@gmail.com \
--cc=lha@kth.se \
/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.