[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Regarding issue #3348 ("Provide syntax which means 'include all files *not* in a changelist'")

From: Bert Huijben <bert_at_qqmail.nl>
Date: Sun, 6 Jan 2013 09:46:20 +0000

How would an old client that links to the 1.7 level api Ďaskí a user
something new during upgrade?

We should just rename the list to something unique or something... Ďsvní
can ask things, but the api canít.
(Other new clients can also ask of course, but in general other api users
canít)

Bert

Sent from Windows Mail

 *From:* C. Michael Pilato
*Sent:* January 6, 2013 4:22 AM
*To:* Julian Foad <julianfoad_at_btopenworld.com>,Daniel Shahaf <
d.s_at_daniel.shahaf.name>,Subversion Development <dev_at_subversion.apache.org>
*Subject:* Re: Regarding issue #3348 ("Provide syntax which means 'include
all files *not* in a changelist'")

On 01/04/2013 05:44 PM, Stefan Sperling wrote:
> On Fri, Jan 04, 2013 at 05:29:30PM -0500, C. Michael Pilato wrote:
>> "--cl=none" -- introduces a reserved changelist name "none" that
>> someone, somewhere might already be really using.
>
> Is this really a problem?
>
> We're bumping the working copy format anyway for 1.8, so the new
> format could start reserving the 'none' changelist. An existing 'none'
> changelist could be detected by 'svn upgrade'. It could then ask the user
> to rename the changelist before upgrading, or even prompt for a new
> name which makes upgrading easier if 1.7 isn't installed anymore.
>
> I like --cl none much better than --cl "".

Oooh... that's a sneaky idea. I rather like it! Doesn't really hope folks
who have scripted processes which involve a changelist named "none", of
course, but we may be well into "edge-case" territory, here.

--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development
Received on 2013-01-06 10:46:53 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.