[p4] Changing default changelist

[Dix, John]

Actually I like the numbered changelists and so do the developers I work
with. It allows them to organize their changes into logical groups. The
number doesn't really mean anything at that point until they become
submitted however I am not sure what else you could substitute for a
number. There's only 26 letters in the English alphabet, basing the
changelist on a description is not the best because it would require you
to type something everytime.

No I think numbering pending changelists is a good idea, I just think a
number should be generated for each one rather than having that extra
step to save as a numbered changelist.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of
todd.benham at kodak.com
Sent: Friday, November 16, 2007 12:54 PM
To: perforce-user at perforce.com
Subject: Re: [p4] Changing default changelist

I have posted about this once before but I will take a chance on be
"flamed" and re-iterate the thought for those who might like to request
this as a feature. (Maybe Perforce support watches these postings
already). 

I think Perforce should be changed to hide this whole issue from the
client. The changelist number should only be assigned when it is
actually
submitted. Any numbers or ids or names would be presented to the user
for
the convenience of the owner but would not have any thing to do with the
final changelist numbers. Thus, the changelist would always be 'new' or
'existing' and not tied to any current value that might change anyway.
Then, both paradigms would/could be available.

Of course, this wouldn't help you solve your problem now.

Todd 


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of
brad.holt at autodesk.com
Sent: Friday, November 16, 2007 1:56 PM
To: Dix, John; perforce-user at perforce.com
Subject: Re: [p4] Changing default changelist


I've thought about that one as well, especially as it makes it easier to
script against not having to account for some other special case pending
change.  However I can also see why the default changelist is just about
necessary as I know folks have written scripts that would make
repetitive
calls to open whole pile of files: p4 open //path/foo1.cpp p4 open
//path/foo2.cpp p4 open //path/foo3.cpp p4 open //path/foo4.cpp ...

This script checking out all half a million files individually without
naming a precreated pending change would permanently eat up all those
changelist numbers and make the user's p4 environment completely
unwieldy
(the UI may not even handle it).

Maybe they could use a new change number each time, but you would be
required to specify "new" with the -c changelist flag to get a new
pending
change number or something.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Dix, John
Sent: Friday, November 16, 2007 9:23 AM
To: Perforce Users Mailing List
Subject: [p4] Changing default changelist

Is there a way to make perforce NEVER use a default changelist and
always
select the next change number in line?

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user