On Sat, Nov 21, 2009 at 08:02:39PM +0100, Martin Furter wrote:
>
>
> On Fri, 20 Nov 2009, Stefan Sperling wrote:
>
> >On Fri, Nov 20, 2009 at 05:36:13AM +0100, Martin Furter wrote:
> >We'd have to store the view name and the associated depths
> >somewhere where we can get at it later.
>
> The a
On Fri, 20 Nov 2009, Stefan Sperling wrote:
On Fri, Nov 20, 2009 at 05:36:13AM +0100, Martin Furter wrote:
Since it's easy to merge views (just add all subdirs of the
requested views and for duplicates let the greater depth win) we
could add support for multiple views in one WC.
I don't see
On Fri, Nov 20, 2009 at 05:36:13AM +0100, Martin Furter wrote:
> >So multiple views can be active at the same time within the same WC?
> >Would this not complicate things a bit too much?
>
> No, they are not 'active in a working' copy, they're not registered
> there. The view just describes what d
On Thu, 19 Nov 2009, Stefan Sperling wrote:
On Thu, Nov 19, 2009 at 05:35:42PM +0100, Martin Furter wrote:
But I thought I'd take the easy route like I did in the python script:
Do a checkout first, then do all the updates needed (it could
ofcourse be integrated into the protocols but that's
Martin Furter wrote:
> Sparse externals!
> /me ducks and watches the set of wooden hammers fly by ;)
They're called "mallets" and are used by carpenters to beat sense into
wood. :)
-- Brane
On Thu, Nov 19, 2009 at 05:35:42PM +0100, Martin Furter wrote:
> I thought long about the property or properties.
>
> My first idea was adding a property "svn:view:NAME" containing only
> one view.
>
> Then I thought about putting all views into "svn:views". But in the
> early days it has been r
On Thu, 19 Nov 2009, C. Michael Pilato wrote:
Martin Furter wrote:
http://svn.apache.org/viewvc/subversion/trunk/tools/client-side/svn-viewspec.py?view=markup
No, I didn't know that script, it's nice.
The only problem I see with that script is that it is a script. If it
were integrated in
Martin Furter wrote:
>> http://svn.apache.org/viewvc/subversion/trunk/tools/client-side/svn-viewspec.py?view=markup
>>
>
> No, I didn't know that script, it's nice.
>
> The only problem I see with that script is that it is a script. If it
> were integrated into subversion all clients can (and pro
Mark Phippard wrote:
As of 1.6, you can in fact use update to make the depth more shallow.
See:
http://blogs.open.collab.net/svn/2009/03/sparse-directories-now-with-exclusion.html
Ooh, nice, I didn't know 'exclude' yet.
My main comment was to ask if you have seen this?
http://svn.apache
Martin Furter wrote:
>
> Hello
>
> I've written a little design document to specify 'views'.
>
> Attached is also a 'proof-of-concept' python script which should behave
> pretty much the same as svn checkout does, except that it supports views
> (it's not very well tested since I'm stuck with sv
On Thu, Nov 19, 2009 at 3:03 AM, Stefan Sperling wrote:
> Also, AFAIK it's currently not possible to update to a more
> shallow depth, but that's a problem with the depth feature rather than
> with views. But we need to specify how "svn update" should behave when
> svn:view properties (or config
On Wed, Nov 18, 2009 at 9:54 PM, Martin Furter wrote:
> I've written a little design document to specify 'views'.
>
> Attached is also a 'proof-of-concept' python script which should behave
> pretty much the same as svn checkout does, except that it supports views
> (it's not very well tested sin
On Thu, Nov 19, 2009 at 03:54:58AM +0100, Martin Furter wrote:
>
> Hello
>
> I've written a little design document to specify 'views'.
>
> Attached is also a 'proof-of-concept' python script which should
> behave pretty much the same as svn checkout does, except that it
> supports views
> (it's
Hello
I've written a little design document to specify 'views'.
Attached is also a 'proof-of-concept' python script which should behave
pretty much the same as svn checkout does, except that it supports views
(it's not very well tested since I'm stuck with svn 1.4 on linux and
had to debug it
14 matches
Mail list logo
