On 23.12.2010 06:09, Peter Samuelson wrote:
> And I still think that 90% of end users, maybe 99%, do _not_ think of
> Subversion as a stack of libraries that just happens to also ship some
> command-line wrapper programs as a convenience. Consequently I think
> they'd prefer the smaller top-level-
[Hyrum K Wright]
> Just curious if this suggestion is made in light of the concerns I
> expressed in the other thread. Namely, that the location of the
> config directory isn't determined until parsing the commandline args,
> at which point it may be too late to introduce the additional args
> ob
On 23.12.2010 01:37, Hyrum K Wright wrote:
> More fallout from my issue #3765 work: I'm investing using ~/.svnrc to
> provide default arguments to the commandline client. In doing so, it
> makes loads of sense not to use the a developer's ~/.svnrc when
> running the tests. Since this is found via
On Wed, Dec 22, 2010 at 9:31 PM, Peter Samuelson wrote:
>
> [Hyrum K Wright]
>> More fallout from my issue #3765 work: I'm investing using ~/.svnrc
>> to provide default arguments to the commandline client. In doing so,
>> it makes loads of sense not to use the a developer's ~/.svnrc when
>> runn
[Hyrum K Wright]
> More fallout from my issue #3765 work: I'm investing using ~/.svnrc
> to provide default arguments to the commandline client. In doing so,
> it makes loads of sense not to use the a developer's ~/.svnrc when
> running the tests.
I'd suggest putting svnrc inside ~/.subversion (
More fallout from my issue #3765 work: I'm investing using ~/.svnrc to
provide default arguments to the commandline client. In doing so, it
makes loads of sense not to use the a developer's ~/.svnrc when
running the tests. Since this is found via the svn_user_get_homedir()
function, which uses th
6 matches
Mail list logo
