Hello all,
[Repost with formatting fixed. Misbehaving email client. ]
What are the currently accepted best practices / tools for maintaining "vendor"
branches? Particularly where maintaining patches against vendor drops is
expected.
I've seen the page at:
http://svnbook.red-bean.com/en/1.7/s
Hello all,
What are the currently accepted best practices / tools for maintaining "vendor"
branches?
I've seen the page
at:http://svnbook.red-bean.com/en/1.7/svn.advanced.vendorbr.html
I ask about updated guidance since:
1) I notice some (?) churn for this section in the SVN Book
repository:http
On Thu, Jan 12, 2012 at 3:41 PM, Andy Levy wrote:
> Have you run svnadmin verify against the *actual* repository?
Yes. No problem detected.
> If you make a new hotcopy of the repository, is that corrupted as well?
>
No. I've only got a corrupted hot copy once in the last two weeks (backups
a
the OS.
Do you still think is was a disk issue?
Thanks,
Dmitry
PS The server is VisualSVN 2.5.2 (Subversion 1.7.2) on WinXP SP3.
On Wed, Jan 11, 2012 at 6:52 PM, Daniel Shahaf wrote:
> D D wrote on Wed, Jan 11, 2012 at 15:51:32 +0400:
> > Once (for now) the verify call failed with
Hi,
My svn backup script calls:
- svnadmin hotcopy
- svnadmin verify (on the copy)
Once (for now) the verify call failed with 'svnadmin: E160004: Revision
file (r2255) lacks trailing newline'
The copy of the repository is still available and I can reproduce the
problem.
The subsequent hot copies
