Re: [PATCH] Add a svnrdump-simulator replaying a dump file for testing.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 23, 2012, 20:38 UTC
- Message-ID
- <7v8veakyar.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <1343074107-23262-1-git-send-email-florian.achleitner.2.6.31@gmail.com>
Florian Achleitner <florian.achleitner.2.6.31@gmail.com> writes:
> To ease testing without depending on a reachable svn server, this > compact python script mimics parts of svnrdumps behaviour. > It requires the remote url to start with sim://. > Eventual slashes at the end of the url are stripped.
s/ventual/xcess/ perhaps?
Show 14 quoted lines
> The url specifies the path of the svn dump file (as created by > svnrdump). Selectable parts of it, or the whole file, are written > to stdout. The part is selectable by giving start and end revision > on the command line. > > Start and end revisions can be specified on the command line > (-rSTART:END, like for svnrdump). > Only revisions between START and excluding END are replayed from > the dumpfile specified by the url. END can also be HEAD. > > If the start revision specified on the command line doesn't exist > in the dump file, it returns 1. > This emulates the behaviour of svnrdump when START>HEAD, i.e. the > requested start revision doesn't exist on the server.
Much more understandable than before.
Show 5 quoted lines
> To allow using the same dump file for simulating multiple > incremental imports the highest visible revision can be limited by > setting the environment variable SVNRMAX to that value. This > effectively limits HEAD to simulate the situation where higher > revs don't exist yet.
It is unclear how this is different from giving the ceiling by specifying it as the "END" in -rSTART:END command line. Is this feature really needed?