- Original Message
> From: Ryan Schmidt
> To: BRM
> On Sep 3, 2010, at 17:52, BRM wrote:
> >> You cannot relocate or update existing working copies. If that's too
> >> restrictive, then yes,
> >> you'll have to skip the dump and load, just change the externals in
> >> HEAD,
>and
On Sep 3, 2010, at 17:52, BRM wrote:
>> You cannot relocate or update existing working copies. If that's too
>> restrictive, then yes,
>> you'll have to skip the dump and load, just change the externals in HEAD,
>> and
>> accept
>> that you can't check out a past revision and have the extern
- Original Message
> From: Ryan Schmidt
> To: BRM
> >> Since the UUID has changed, everyone must check out new working copies;
> >> it
>is
>
> >> not possible to update or switch existing working copies to this new
>changed
>
> >> repository.
> >
> > Or I could just ignore th
Ryan Schmidt wrote on Fri, Sep 03, 2010 at 16:57:31 -0500:
>
> On Sep 3, 2010, at 16:51, Daniel Shahaf wrote:
>
> > Ryan Schmidt wrote on Fri, Sep 03, 2010 at 15:29:17 -0500:
> >
> >> the dump format does not include information
> >> about hook scripts, config files or locks. If you dump and loa
On Sep 3, 2010, at 16:51, Daniel Shahaf wrote:
> Ryan Schmidt wrote on Fri, Sep 03, 2010 at 15:29:17 -0500:
>
>> the dump format does not include information
>> about hook scripts, config files or locks. If you dump and load, the new
>> repository will have the default hook script templates (so,
Ryan Schmidt wrote on Fri, Sep 03, 2010 at 15:29:17 -0500:
> the dump format does not include information
> about hook scripts, config files or locks. If you dump and load, the new
> repository will have the default hook script templates (so, no hook scripts),
> the default configuration, and nothi
On Sep 3, 2010, at 08:36, BRM wrote:
>> Do not use sed to edit a dumpfile. Use a tool designed for the task, like
>> svndumptool.
>> http://svn.borg.ch/svndumptool/
>
> Why? B/c it might change data in files too? That's actually something I want
> done.
> My prime repository has some scripts
BRM wrote on Fri, Sep 03, 2010 at 06:36:05 -0700:
> - Original Message
>
> > From: Ryan Schmidt
> > > $ cat Example1.dump | sed
> > > 's/file:\/\/\/svnTest\/Example1/file:\/\/\/svnTest\/Example2/' >
> > > Example1-edited.dump
> > Do not use sed to edit a dumpfile. Use a tool designe
On Fri, Sep 3, 2010 at 09:36, BRM wrote:
> - Original Message
>
>> From: Ryan Schmidt
>> > $ cat Example1.dump | sed
>> > 's/file:\/\/\/svnTest\/Example1/file:\/\/\/svnTest\/Example2/' >
>> > Example1-edited.dump
>> Do not use sed to edit a dumpfile. Use a tool designed for the task,
- Original Message
> From: Ryan Schmidt
> > $ cat Example1.dump | sed
> > 's/file:\/\/\/svnTest\/Example1/file:\/\/\/svnTest\/Example2/' >
> > Example1-edited.dump
> Do not use sed to edit a dumpfile. Use a tool designed for the task, like
>svndumptool.
> http://svn.borg.ch/svndum
On Sep 2, 2010, at 18:51, BRM wrote:
> - Original Message
>
>> From: BRM
>> To: Ryan Schmidt
>> - Original Message
>>> On Sep 2, 2010, at 11:27, BRM wrote:
>>> If you can afford to have the repository offline, make a dumpfile, twiddle
>>> it, load it into a new repository,
- Original Message
> From: BRM
> To: Ryan Schmidt
> - Original Message
> > On Sep 2, 2010, at 11:27, BRM wrote:
> > If you can afford to have the repository offline, make a dumpfile,
> > twiddle
>it, load it
> > into a new repository, and have everybody check out new wor
- Original Message
> On Sep 2, 2010, at 11:27, BRM wrote:
> > I recently had my subversion server die - the box, not subversion itself -
>and
>
> > have been working through the recovery process.
> > Part of that is going through and modifying a number of projects for the
>change
>
On Sep 2, 2010, at 11:27, BRM wrote:
> I recently had my subversion server die - the box, not subversion itself -
> and
> have been working through the recovery process.
> Part of that is going through and modifying a number of projects for the
> change
> in the URL - namely changing from a n
On Thu, Sep 2, 2010 at 12:27, BRM wrote:
> I recently had my subversion server die - the box, not subversion itself - and
> have been working through the recovery process.
> Part of that is going through and modifying a number of projects for the
> change
> in the URL - namely changing from a non
I recently had my subversion server die - the box, not subversion itself - and
have been working through the recovery process.
Part of that is going through and modifying a number of projects for the change
in the URL - namely changing from a non-standard port for apache to a standard
port.
We h
16 matches
Mail list logo
