On Thu, Oct 6, 2016 at 4:26 PM, wrote:
> Is it possible that old data are deleted subversion after a while?
> I've experienced that with 2014 data back, you know it is?
No, not automatically, not without a serious effort. (The only way to
delete old data is to dump, filter and load the repositor
Hello,
Is it possible that old data are deleted subversion after a while?
I've experienced that with 2014 data back, you know it is?
Greetings, I hope your answers.
Joseph
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: dinsdag 26 juni 2012 22:14
> To: kmra...@rockwellcollins.com
> Cc: Mark Phippard; Trent Fisher; users@subversion.apache.org
> Subject: Re: Possible svnsync data loss bug?
>
> On Tue,
On Wed, Jun 27, 2012 at 11:55:33AM -0400, Trent Fisher wrote:
> On 06/26/2012 05:02 PM, Stefan Sperling wrote:
> >On Tue, Jun 26, 2012 at 10:13:50PM +0200, Johan Corveleyn wrote:
> >>On Tue, Jun 26, 2012 at 8:07 PM, wrote:
> >>>Any reason svnsync couldn't grow a "--fail-on-access-error" option?
>
On 06/26/2012 05:02 PM, Stefan Sperling wrote:
On Tue, Jun 26, 2012 at 10:13:50PM +0200, Johan Corveleyn wrote:
On Tue, Jun 26, 2012 at 8:07 PM, wrote:
Any reason svnsync couldn't grow a "--fail-on-access-error" option?
Sure, I think that could be useful (as long as it's not the default
(back
On Jun 26, 2012, at 6:43 PM, Ryan Schmidt
wrote:
>
> On Jun 26, 2012, at 12:43, Mark Phippard wrote:
>
>> I cannot speak to all scenarios because I have not tested them. For
>> example, if the svnsync user simply had no read access to anywhere in
>> the repository it seems like it ought to er
On Jun 26, 2012, at 12:43, Mark Phippard wrote:
> I cannot speak to all scenarios because I have not tested them. For
> example, if the svnsync user simply had no read access to anywhere in
> the repository it seems like it ought to error. But that scenario
> aside, the way that svnsync works i
On Tue, Jun 26, 2012 at 10:13:50PM +0200, Johan Corveleyn wrote:
> On Tue, Jun 26, 2012 at 8:07 PM, wrote:
> > Any reason svnsync couldn't grow a "--fail-on-access-error" option?
>
> Sure, I think that could be useful (as long as it's not the default
> (backwards compat)).
Would printing a warn
On Tue, Jun 26, 2012 at 8:07 PM, wrote:
>> > I was about to ask if svnsync would get access denied errors... but I
>> > did
>> > another test which, I think, answered my own question: If I run "svn
>> > log"
>> > against a repository to which I have only access to part of, revs in the
>> > areas
> > I was about to ask if svnsync would get access denied errors... but I
did
> > another test which, I think, answered my own question: If I run "svn
log"
> > against a repository to which I have only access to part of, revs in
the
> > areas I don't have access to will show up as "(no author)
On Fri, Jun 22, 2012 at 5:21 PM, Trent Fisher wrote:
> I was about to ask if svnsync would get access denied errors... but I did
> another test which, I think, answered my own question: If I run "svn log"
> against a repository to which I have only access to part of, revs in the
> areas I don't
On 06/22/2012 08:17 PM, Nico Kadel-Garcia wrote:
On Fri, Jun 22, 2012 at 5:21 PM, Trent Fisher wrote:
On 06/22/2012 01:59 PM, Mark Phippard wrote:
On Fri, Jun 22, 2012 at 1:52 PM, Trent Fisher
wrote:
I just ran into a rather frightening problem. We do replications via
svnsync for backup p
On Fri, Jun 22, 2012 at 5:21 PM, Trent Fisher wrote:
>
> On 06/22/2012 01:59 PM, Mark Phippard wrote:
>>
>> On Fri, Jun 22, 2012 at 1:52 PM, Trent Fisher
>> wrote:
>>>
>>> I just ran into a rather frightening problem. We do replications via
>>> svnsync for backup purposes. I just found two of t
On 06/22/2012 01:59 PM, Mark Phippard wrote:
On Fri, Jun 22, 2012 at 1:52 PM, Trent Fisher wrote:
I just ran into a rather frightening problem. We do replications via
svnsync for backup purposes. I just found two of the replicated
repositories which had these entries for *every* version:
On Fri, Jun 22, 2012 at 1:52 PM, Trent Fisher wrote:
> I just ran into a rather frightening problem. We do replications via
> svnsync for backup purposes. I just found two of the replicated
> repositories which had these entries for *every* version:
>
> r20927 | (no author) | (no date) | 1 line
I just ran into a rather frightening problem. We do replications via
svnsync for backup purposes. I just found two of the replicated
repositories which had these entries for *every* version:
r20927 | (no author) | (no date) | 1 line
Changed paths:
And svnlook tree shows there is nothing
16 matches
Mail list logo
