Hi there,
my situation is as follows:
there's a large svn repository
svn+ssh://someserver/reps/maindir/
I only work with the subdirectory
svn+ssh://someserver/reps/maindir/old_dir/foobar/what_I_work_with
such that I used to check it out with
svn co svn+ssh://someserver/reps/maindir/old_dir/foobar
> Hi there,
>
> my situation is as follows:
> there's a large svn repository
> svn+ssh://someserver/reps/maindir/
> I only work with the subdirectory
> svn+ssh://someserver/reps/maindir/old_dir/foobar/what_I_work_with
>
> such that I used to check it out with
> svn co svn+ssh://someserver/reps/ma
> > Hi there,
> >
> > my situation is as follows:
> > there's a large svn repository
> > svn+ssh://someserver/reps/maindir/
> > I only work with the subdirectory
> > svn+ssh://someserver/reps/maindir/old_dir/foobar/what_I_work_with
> >
> > such that I used to check it out with
> > svn co
> > svn+ss
On Wed, Jul 24, 2013 at 05:04:13PM +0200, Paul Seyfert wrote:
> Is there any way to check out or update to revision r900?
Do you know about peg revisions?
http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
>
> Oh, and you can of course check out the deleted path... just provide the peg
> revision...
>
> Svn co ^path/to/file@900
>
> BOb
>
Hi,
@BOb
Thanks! Exactly what I needed!
@Stefan
no I didn't know about peg revisions. Thanks for the pointer!
Paul
I'm happy to announce the release of Apache Subversion 1.7.11.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download/#supported-releases
This release addresses one security issue:
CVE-2013-4131: mod_dav_svn assertion from requests against root path.
M
I'm happy to announce the release of Apache Subversion 1.8.1.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download/#recommended-release
This release addresses one security issue:
CVE-2013-4131: mod_dav_svn assertion from requests against root path.
M
Hi,
I am getting the following error when I am trying to commit:
svn: Commit failed (details follow):
svn: Can't move '/.../db/txn-protorevs/5-9.rev' to '/.../db/revs/0/6':
Remote I/O error
Please help.
Thanks,
Prateeti Mohapatra
Guten Tag Prateeti Mohapatra,
am Mittwoch, 24. Juli 2013 um 19:26 schrieben Sie:
> svn: Commit failed (details follow):
> svn: Can't move '/.../db/txn-protorevs/5-9.rev' to
> '/.../db/revs/0/6': Remote I/O error
This is something you should your server/repo admins first, there
surely is something
I'm planning my upgrade to SVN 1.8 & to go along with it, setting up a
new backup process. Here's what I'm thinking:
* Monday overnight, take a full backup (svnadmin hotcopy, then
compress the result for storage)
* Tuesday through Sunday overnights, incremental backups (svnadmin
dump --incremental
On Wed, Jul 24, 2013 at 2:59 PM, Andy Levy wrote:
> I'm planning my upgrade to SVN 1.8 & to go along with it, setting up a
> new backup process. Here's what I'm thinking:
>
> * Monday overnight, take a full backup (svnadmin hotcopy, then
> compress the result for storage)
> * Tuesday through Sunda
On 7/24/2013 2:59 PM, Andy Levy wrote:
I'm planning my upgrade to SVN 1.8 & to go along with it, setting up a
new backup process. Here's what I'm thinking:
* Monday overnight, take a full backup (svnadmin hotcopy, then
compress the result for storage)
* Tuesday through Sunday overnights, increme
The enhancement would be to include only parents marked for addition. Nothing
special for prop changes as you don't want to commit these later if the
directory was already committed (unless explicitly stated).
So, I think's a rather simple request. If commit --parents is loaded then any
paren
On Wed, Jul 24, 2013 at 2:22 PM, Thomas Harold wrote:
> >
> What we might do once 1.8 server is stable is switch to doing the new
> "incremental" style hotcopy on Mon-Sat evenings and do a full hotcopy on
> Sun. Right now, we address the time it takes to do full hotcopy of all 300+
> repositories
On Wed, Jul 24, 2013 at 07:32:20PM +, Braun, Eric wrote:
> The enhancement would be to include only parents marked for addition.
> Nothing special for prop changes as you don't want to commit these later if
> the directory was already committed (unless explicitly stated).
>
> So, I think's
On Wed, Jul 24, 2013 at 2:59 PM, Andy Levy wrote:
> I'm planning my upgrade to SVN 1.8 & to go along with it, setting up a
> new backup process. Here's what I'm thinking:
>
> * Monday overnight, take a full backup (svnadmin hotcopy, then
> compress the result for storage)
Insufficient. You also n
16 matches
Mail list logo