On Tue, 16 May 2006, Ben Collins-Sussman wrote:
> On 5/16/06, Philip Martin <firstname.lastname@example.org> wrote:
> >Related questions: do users expect to add files to a changeset before
> >modifying them (much like the lock command) or is it something that
> >gets done after the file has been modified?
> Association with a changelist is a piece of temporary metadata which
> is orthogonal to the file being modifed or not. You can (de)associate
> a changelist at any time.
> Note that this is a bit different than perforce, but I don't think
> that's a bad thing. In perforce, a file is read-only until you 'p4
> edit' it, which automatically causes the file to be associated with a
> changelist. (If no changelist is specified by the user, then the file
> becomes associated with a changelist named 'default'.)
> >Should the command that
> >adds files to a changeset skip unmodified files?
> No. There's nothing wrong with attaching a changelist name to an
> unmodified file.
+1 to all of the above.
> >If it doesn't skip
> >then what about if/when the command becomes recursive?
> In the case of recursion, the only things that should be skipped, I
> think, are unversioned items.
I take it that an unversioned item cannot become part of a change list
in the first place? Assuming so, +1.
Received on Thu May 18 19:27:22 2006
- application/pgp-signature attachment: stored