You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "C. Michael Pilato" <cm...@collab.net> on 2011/02/10 17:34:46 UTC
Re: Requesting a New Feature
Now tracked as http://subversion.tigris.org/issues/show_bug.cgi?id=3804
On 07/29/2010 10:14 AM, C. Michael Pilato wrote:
> Sorta kinda. Let's use our own tree as an example. We start with an empty
> checkout of the root of our project:
>
> $ svn co --depth empty http://svn.apache.org/repos/asf/subversion \
> subversion
> $ cd subversion
>
> Now you decide that you want the trunk code for our cmdline tests (and only
> that code). You can do this today by the following lengthy process:
>
> $ svn up --depth empty trunk
> $ svn up --depth empty trunk/subversion
> $ svn up --depth empty trunk/subversion/tests
> $ svn up trunk/subversion/tests/cmdline
>
> (IIRC, --depth and --set-depth are equivalent here because this behavior is
> more checkout-like than update-like.)
>
> Alternatively, I *suspect* you could do this:
>
> $ svn up --depth empty trunk trunk/subversion trunk/subversion/tests
> $ svn up trunk/subversion/tests/cmdline
>
> So, fewer commands, but still an annoying approach. Elango is wondering why
> 'svn update' doesn't add missing-but-needed parent directories (at
> depth=empty) by default. Why can't the above be shortened to just:
>
> $ svn up trunk/subversion/tests/cmdline
>
> ?
>
> I think that's a fair question to ask. Note that if we like the idea but
> don't wish to make it the default behavior, we have the --parents option we
> can employ here to toggle it:
>
> $ svn up --parents trunk/subversion/tests/cmdline
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: Requesting a New Feature
Posted by Stefan Küng <to...@gmail.com>.
On Thu, Feb 10, 2011 at 18:34, Julian Foad <ju...@wandisco.com> wrote:
> On Thu, 2011-02-10, C. Michael Pilato wrote:
>> Now tracked as http://subversion.tigris.org/issues/show_bug.cgi?id=3804
>>
>> On 07/29/2010 10:14 AM, C. Michael Pilato wrote:
>> > Sorta kinda. Let's use our own tree as an example. We start with an empty
>> > checkout of the root of our project:
>> >
>> > $ svn co --depth empty http://svn.apache.org/repos/asf/subversion \
>> > subversion
>> > $ cd subversion
>> >
>> > Now you decide that you want the trunk code for our cmdline tests (and only
>> > that code). You can do this today by the following lengthy process:
>> >
>> > $ svn up --depth empty trunk
>> > $ svn up --depth empty trunk/subversion
>> > $ svn up --depth empty trunk/subversion/tests
>> > $ svn up trunk/subversion/tests/cmdline
>> >
>> > (IIRC, --depth and --set-depth are equivalent here because this behavior is
>> > more checkout-like than update-like.)
>> >
>> > Alternatively, I *suspect* you could do this:
>> >
>> > $ svn up --depth empty trunk trunk/subversion trunk/subversion/tests
>> > $ svn up trunk/subversion/tests/cmdline
>> >
>> > So, fewer commands, but still an annoying approach. Elango is wondering why
>> > 'svn update' doesn't add missing-but-needed parent directories (at
>> > depth=empty) by default. Why can't the above be shortened to just:
>> >
>> > $ svn up trunk/subversion/tests/cmdline
>> >
>> > ?
>> >
>> > I think that's a fair question to ask. Note that if we like the idea but
>> > don't wish to make it the default behavior, we have the --parents option we
>> > can employ here to toggle it:
>> >
>> > $ svn up --parents trunk/subversion/tests/cmdline
>
> +1 to doing this, with the "--parents" flag required. (Given that we
> already use --parents in other subcommands, it would feel unnecessary
> and inconsistent not to require it here.)
>
> p.s. C-Mike, did I dream it, or did you implement something similar just
> a few weeks ago? Maybe --parents for another subcommand?
I'm confused, isn't this already implemented?
svn_client_update4() has a parameter 'makeparents' for which the docs tell:
* If @a make_parents is TRUE, create any non-existent parent
* directories also by checking them out at depth=empty.
it mentions "parent directories" (plural), so I would assume that this
already should be implemented as requested?
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Re: Requesting a New Feature
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 02/10/2011 02:49 PM, Bob Archer wrote:
>> On 02/10/2011 12:34 PM, Julian Foad wrote:
>>> p.s. C-Mike, did I dream it, or did you implement something
>> similar
>>> just a few weeks ago? Maybe --parents for another subcommand?
>>
>> Wow. I mean ... just ... wow.
>>
>> /me cries.
>
> Is that a yea or nay?
Yes, I implemented this already. See issue #3748.
http://subversion.tigris.org/issues/show_bug.cgi?id=3748
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
RE: Requesting a New Feature
Posted by Bob Archer <Bo...@amsi.com>.
> On 02/10/2011 12:34 PM, Julian Foad wrote:
> > p.s. C-Mike, did I dream it, or did you implement something
> similar
> > just a few weeks ago? Maybe --parents for another subcommand?
>
> Wow. I mean ... just ... wow.
>
> /me cries.
Is that a yea or nay?
BOb
Re: Requesting a New Feature
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 02/10/2011 02:54 PM, Mark Phippard wrote:
> On Thu, Feb 10, 2011 at 2:48 PM, C. Michael Pilato <cm...@collab.net> wrote:
>> On 02/10/2011 12:34 PM, Julian Foad wrote:
>>> p.s. C-Mike, did I dream it, or did you implement something similar just
>>> a few weeks ago? Maybe --parents for another subcommand?
>>
>> Wow. I mean ... just ... wow.
>>
>> /me cries.
>
> That is what you get for going through old emails.
Indeed!
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: Requesting a New Feature
Posted by Mark Phippard <ma...@gmail.com>.
On Thu, Feb 10, 2011 at 2:48 PM, C. Michael Pilato <cm...@collab.net> wrote:
> On 02/10/2011 12:34 PM, Julian Foad wrote:
>> p.s. C-Mike, did I dream it, or did you implement something similar just
>> a few weeks ago? Maybe --parents for another subcommand?
>
> Wow. I mean ... just ... wow.
>
> /me cries.
That is what you get for going through old emails.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Re: Requesting a New Feature
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 02/10/2011 12:34 PM, Julian Foad wrote:
> p.s. C-Mike, did I dream it, or did you implement something similar just
> a few weeks ago? Maybe --parents for another subcommand?
Wow. I mean ... just ... wow.
/me cries.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: Requesting a New Feature
Posted by Julian Foad <ju...@wandisco.com>.
On Thu, 2011-02-10, C. Michael Pilato wrote:
> Now tracked as http://subversion.tigris.org/issues/show_bug.cgi?id=3804
>
> On 07/29/2010 10:14 AM, C. Michael Pilato wrote:
> > Sorta kinda. Let's use our own tree as an example. We start with an empty
> > checkout of the root of our project:
> >
> > $ svn co --depth empty http://svn.apache.org/repos/asf/subversion \
> > subversion
> > $ cd subversion
> >
> > Now you decide that you want the trunk code for our cmdline tests (and only
> > that code). You can do this today by the following lengthy process:
> >
> > $ svn up --depth empty trunk
> > $ svn up --depth empty trunk/subversion
> > $ svn up --depth empty trunk/subversion/tests
> > $ svn up trunk/subversion/tests/cmdline
> >
> > (IIRC, --depth and --set-depth are equivalent here because this behavior is
> > more checkout-like than update-like.)
> >
> > Alternatively, I *suspect* you could do this:
> >
> > $ svn up --depth empty trunk trunk/subversion trunk/subversion/tests
> > $ svn up trunk/subversion/tests/cmdline
> >
> > So, fewer commands, but still an annoying approach. Elango is wondering why
> > 'svn update' doesn't add missing-but-needed parent directories (at
> > depth=empty) by default. Why can't the above be shortened to just:
> >
> > $ svn up trunk/subversion/tests/cmdline
> >
> > ?
> >
> > I think that's a fair question to ask. Note that if we like the idea but
> > don't wish to make it the default behavior, we have the --parents option we
> > can employ here to toggle it:
> >
> > $ svn up --parents trunk/subversion/tests/cmdline
+1 to doing this, with the "--parents" flag required. (Given that we
already use --parents in other subcommands, it would feel unnecessary
and inconsistent not to require it here.)
p.s. C-Mike, did I dream it, or did you implement something similar just
a few weeks ago? Maybe --parents for another subcommand?
- Julian