>
> This is an old idea. If you want to implement it, a file is not the
> right place for the view definition; a property on a directory might be.
>
A Svn property that sets for the user and workspace only, and retains no
history, right? Meaning if the user had two checkouts of the same Svn URL,
On 13.09.2017 09:25, Paul Hammant wrote:
>
> This is an old idea. If you want to implement it, a file is not the
> right place for the view definition; a property on a directory
> might be.
>
>
> A Svn property that sets for the user and workspace only, and retains
> no history, right?
Have you seen:
http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py
> On Sep 12, 2017, at 10:22 PM, Paul Hammant wrote:
>
> Compared to Perforce's client-spec, Subversion's sparse checkouts are quite
> cumbersome:
>
> svn checkout http://svn.apache.org/repos/as
> > This is an old idea. If you want to implement it, a file is not the
> > right place for the view definition; a property on a directory
> > might be.
> >
> >
> > A Svn property that sets for the user and workspace only, and retains
> > no history, right? Meaning if the user had two
>
>
> http://svn.apache.org/repos/asf/subversion/trunk/tools/
> client-side/svn-viewspec.py
>
>
Excellent!
I see you posted a StackOverflow answer on that too, Mark -
https://stackoverflow.com/questions/7481860/create-folder-structure-based-on-file
I'm one of those people that's blind to a lib or
Oh tools/client-side/svn-viewspec.py doesn't have any tests :-(
The good news is that it can be refactored to have test quite easily. I
think I'll be able to donate some code.
On Wed, Sep 13, 2017 at 06:53:14AM -0400, Paul Hammant wrote:
> Oh tools/client-side/svn-viewspec.py doesn't have any tests :-(
>
> The good news is that it can be refactored to have test quite easily. I
> think I'll be able to donate some code.
I would also be happy to see further improvements t
I have a test for the inlined example. Well it would pass, but PyTest's
assert function is about 10x inferior to JUnit's or Hamcrest's
assertEquals() and isn't telling me where I've futzed up a CR somewhere.
This even *with* optional args (that should be mandatory -s and -vv). Gotta
go to work now
T'was line endings and redundant spaces, fixed with a strip(), but as I
say, Java's asserts are better to noobs.
Here's the test:
https://gist.github.com/paul-hammant/058161485a227299e5d7c34cc6a33264
I had to refactor the actual script too. A tiny backwards-compatible bit.
-ph
OK, so I am up at 93% coverage with a PyTest script. As an Apache Member
I'm already CLA'd. I could start to write tests that break the script in
ways that it should handle more gracefully, but I need assurance that I'm
not wasting my time.
I'm not expecting committership (especially since my last
On 13.09.2017 12:40, Paul Hammant wrote:
>
> > This is an old idea. If you want to implement it, a file is
> not the
> > right place for the view definition; a property on a directory
> > might be.
> >
> >
> > A Svn property that sets for the user and workspa
On 13.09.2017 19:47, Paul Hammant wrote:
> OK, so I am up at 93% coverage with a PyTest script. As an Apache
> Member I'm already CLA'd. I could start to write tests that break the
> script in ways that it should handle more gracefully, but I need
> assurance that I'm not wasting my time.
>
> I'm n
As you may have noticed, I started implementing support for multiple WC
formats on the better-pristines branch, as a prelude to adding support
for compressed pristines without forcing users to upgrade all their
working copies. There's an overview in the branch readme file, but the
basic idea is thi
13 matches
Mail list logo
