On 2001-08-02 15:51:43 Ben Collins-Sussman wrote:
><peter.westlake@arm.com> writes:
>
>> >If I were to leave off the '-d' argument to checkout:
>> >
>> > $ svn checkout http://foo.com/svn/repo/trunk/paint
>> >
>> > paint/Makefile
>> > paint/canvas.c
>> > ...
>>
>> Hmm... so what rune would get you
>>
>> trunk/paint/Makefile
>> trunk/paint/canvas.c
>> ...
>
> $ svn checkout http://foo.com/svn/repo/trunk
>
> ...assuming that there are no other siblings of "paint" in trunk.
Wrong assumption :-)
I'm after the case where there *are* siblings, but I don't want them all.
I want to work on more than one branch, so I have a directory for each,
and what better than to use the repository's own structure? So I want
"trunk", and I don't want to have to remember it and type it when the
repository knows it already.
...
>Like I said, we've been planning on replacing branches and tags with
>this "clone" model for over a year, and after we hit M3 on August
>15th, this is really the last Huge Task we need to do before getting
>to Alpha in mid-September. Obviously, the filesystem already supports
>cloning. The Huge Task at hand is writing *client-side* support for
>clones. It's a big UI problem, and it's also going to be painful to
>write support for things like:
>
> * switching your working copy onto a related clone (branch)
> * allowing client-side merging of two clones (branches)
>
>We would absolutely love it if you're willing to volunteer to help us
>flesh-out use cases and examples! We've been somewhat documenting
>client-side behaviors in our doc/user/manual/ directory, but no doubt
>that we really need intense documentation for this new way of working.
>If you're willing to write documentation, that would be fantastic.
I would love to contribute to this. Even if we choose a different
source control system, I shall be thinking about Subversion in my
spare time, and I would be happy to work out use cases and examples.
The chance to influence the UI is a wonderful opportunity too.
Peter.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:34 2006