On Dec 28, 2011, at 09:09, Andreas Du Rietz wrote:
> We use SVN 1.4 (I know, we should upgrade).
Yes you should, because as per the Subversion 1.6 release notes (and we're up
to 1.7 now), Subversion 1.4 is no longer supported:
http://subversion.apache.org/docs/release-notes/1.6.html#svn-1.4-d
On Nov 1, 3:02 pm, Douglas Wilson wrote:
> On Oct 22, 2:25 am, Stefan Sperling wrote:
> > Your reproduction recipe is incomplete.
>
> I think I left out the import..lemme try again:
...snip...
It looks like this is covered by issues 4056 and 4057 and targeted for
release 1.8.
Guess I'll just
> > Hello,
> >
> > Thanks for your reply! Difference is that before, after doing update
> > or check out with -N, i can do one svn update in the root. Now update
> > in the root starts updating tags.
> >
> > Please note that i have a bunch of projects and doing update for every
> > trunk is tiresom
I just completed my worst merge yet, or so I thought. We use SVN 1.4 (I
know, we should upgrade). The branch has been synched multiple times with
trunk so I used this approach:
Merge a range of revisions, not including the merge from trunk.
No commit
Merge another range of revisions skipping the r
> > Hello,
> >
> > Thanks for your reply! Difference is that before, after doing update
> > or check out with -N, i can do one svn update in the root. Now update
> > in the root starts updating tags.
> >
> > Please note that i have a bunch of projects and doing update for every
> > trunk is tiresom
>
> From: Pavel krupets
> Sent: 12/28/2011 9:16
> To: Bob Archer; users@subversion.apache.org
> Subject: RE: svn update issues...
> Hello,
>
> Thanks for your reply! Difference is that before, after doing update or check
> out with -N, i can do one svn upda
>
> From: Pavel krupets
> Sent: 12/28/2011 9:16
> To: Bob Archer; users@subversion.apache.org
> Subject: RE: svn update issues...
> Hello,
>
> Thanks for your reply! Difference is that before, after doing update or check
> out with -N, i can do one svn upda
> From: Bob Archer
> Sent: 12/28/2011 9:02
> To: Pavel Krupets; users@subversion.apache.org
> Subject: RE: svn update issues...
>
> > > I have the following "structure":
> > >
> > > [+] \
> > > [+] tags
> > > [+] 2011-01-01 ...
> > > [+] ...
> > > [+] trunk
> > > [+] ...
> > >
> >
Hello,
Thanks for your reply! Difference is that before, after doing update or check
out with -N, i can do one svn update in the root. Now update in the root starts
updating tags.
Please note that i have a bunch of projects and doing update for every trunk is
tiresome.
Reverted to using 1.6.
> > I have the following "structure":
> >
> > [+] \
> > [+] tags
> > [+] 2011-01-01 ...
> > [+] ...
> > [+] trunk
> > [+] ...
> >
> > Before I was able to do:
> >
> > 1) svn co -N http://me/svn .
> > 2) svn update -N tags
> > 3) svn update trunk
> >
> > Then when I decided to update
> I have the following "structure":
>
> [+] \
> [+] tags
> [+] 2011-01-01 ...
> [+] ...
> [+] trunk
> [+] ...
>
> Before I was able to do:
>
> 1) svn co -N http://me/svn .
> 2) svn update -N tags
> 3) svn update trunk
>
> Then when I decided to update my stuff I just go there an
On Dec 24, 2011, at 11:21 AM, Daniel Shahaf wrote:
> Could you file an issue, please, and assign it to the 1.8.0 milestone?
Done. http://subversion.tigris.org/issues/show_bug.cgi?id=4088
Jan Keirse wrote on Wed, Dec 28, 2011 at 11:44:49 +0100:
> Hello,
>
> I have a master and a slave. Now I want to discard the current master
> and start using the slave as the new master (creating a new slave on
> another server and stop the server that currently runs the master.)
>
> I think the
Sébastien Brisard wrote on Tue, Dec 27, 2011 at 21:39:52 +0100:
> >> Should I move to svn 1.7 ?
> >>
> >
> > You could try moving to 1.7, and/or using the official JavaHL bindings
> > instead of the third-party SVNKit implementation. With my svn hat on,
> > though, I'd like to figure out how those
Hello,
I have a master and a slave. Now I want to discard the current master
and start using the slave as the new master (creating a new slave on
another server and stop the server that currently runs the master.)
I think the steps to do this are the following:
* Change authz on the master so tha
15 matches
Mail list logo
