[p4] Changing default changelist

Ivey, William william_ivey at bmc.com
Sun Nov 18 10:39:14 PST 2007


> I just think a number should be generated for each one

I vote nay to that, except as an option. That "feature" would
assume you know ahead of time all the files that may need to be
checked out for a given change, otherwise you have to remember
to checkout additional files to the same numbered changelist
that was generated automatically for the first batch of files.

This may not be an issue for new development, but for maintenance,
where the extent of the required changes may not be obvious when
you begin work, it would be a pain. Worse, you might end up
submitting part of the change, having forgotten to consolidate
your work into one changelist.

I find the current system works just fine. Automated processes
can easily generate numbered changelists and users can always
move files opened in the default changelist to a numbered
changelist as needed, assuming they don't open files into it
to begin with.

A feature I'd reather see is a shorthand command to list my
current numbered changelists with the first n characters of
the comment and, as an option, the affected files.

-Wm


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of 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.



More information about the perforce-user mailing list