On Mon, Jun 25, 2012 at 3:30 PM, wrote:
> Hello,
>
> I just got through reading the "How to report a bug" page but what I have is
> more of an enhancement request. Not sure if it belongs here but I'll
> writeup either way just in case.
>
> I am fairly new to Subversion but have nearly 20 years e
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
On Tue, Jun 26, 2012 at 5:39 PM, Phil Pinkerton wrote:
> Any particular reason I cannot view/annotate a shell script using the latest
> ViewVC provided with Subversion Edge ?
>
Maybe Subversion (or ViewVC) thinks it's not text for some reason?
Maybe check the svn:mime-type property on the file o
> > 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
Any particular reason I cannot view/annotate a shell script using the latest
ViewVC provided with Subversion Edge ?
Phil
On Tue, Jun 26, 2012 at 02:50:33PM +, Mark Bertenshaw wrote:
> Stefan -
>
> Thanks verifying this point. As a related matter, the error code returned in
> my case just happened to be 1. Is there a list of standard error codes
> returned from SVN ?
I believe it is always either 0 or 1 at the
Guten Tag Mark Bertenshaw,
am Dienstag, 26. Juni 2012 um 16:38 schrieben Sie:
> On the other hand, I can't find an
> option for SVN ADD which says "ignore versioned files".
I think --force is what you're looking for.
svn help add
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schönin
Stefan -
Thanks verifying this point. As a related matter, the error code returned in my
case just happened to be 1. Is there a list of standard error codes returned
from SVN ?
Regards,
--
Mark Bertenshaw
-Original Message-
From: Stefan Sperling [mailto:s...@elego.de]
Sent: 26 June 2
On Tue, Jun 26, 2012 at 01:58:56PM +, Mark Bertenshaw wrote:
> Hi -
>
> I have just cleared up a build issue which resulted from upgrading from
> Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
> newly created component logs with:
>
> SVN ADD -q $APPROOT/LOG
Hi -
I have just cleared up a build issue which resulted from upgrading from
Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
newly created component logs with:
SVN ADD -q $APPROOT/LOGS/*
In both versions of Subversion, this raises an error saying that the log f
Please send plain text to the mailing list.
On Tue, Jun 26, 2012 at 9:58 AM, Mark Bertenshaw
wrote:
>
> Hi -
>
>
>
> I have just cleared up a build issue which resulted from upgrading from
> Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
> newly created component l
Hi -
I have just cleared up a build issue which resulted from upgrading from
Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
newly created component logs with:
SVN ADD -q $APPROOT/LOGS/*
In both versions of Subversion, this raises an error saying that the log f
The nested status is a TortoiseSVN specific status that tells you that there
is a working copy below the parent working copy (a ‘nested’ working copy).
This is exactly how externals are implemented in Subversion, so I would
recommend leaving it at this.
Bert
From: 許阿光 [mail
From: Stefan Sperling [s...@elego.de]
Sent: 26 June 2012 10:06
To: James French
Cc: users@subversion.apache.org
Subject: Re: moving files in repobrowser generates mergeinfo
On Tue, Jun 26, 2012 at 09:47:06AM +0100, James French wrote:
> Thanks Stefan. I wi
On Tue, Jun 26, 2012 at 09:47:06AM +0100, James French wrote:
> Thanks Stefan. I wish it didn't add that mergeinfo. Actually if mergeinfo was
> entirely internal I wouldn't care what it did (as long as it worked). Its all
> the checkin clutter that upsets me.
How much clutter do you have? If you
From: Stefan Sperling [s...@elego.de]
Sent: 25 June 2012 18:59
To: James French; users@subversion.apache.org
Subject: Re: moving files in repobrowser generates mergeinfo
On Mon, Jun 25, 2012 at 07:55:05PM +0200, Stefan Sperling wrote:
> On Mon, Jun 25, 201
Hello Johan,
Yes, you understood my request correctly. I will create an issue today.
Regarding the implementation a simple, automatic replacement of "-rHEAD
path@peg" by "-r{revision of HEAD} path@peg" on each access should do the job
perfectly (plus parser modification of course).
Thank you a
22 matches
Mail list logo
