"Martin Letenay" <mle@whitestein.com> wrote on 09/29/2005 08:25:34 AM:
> I think I'm starting to dislike the current behavior of dirty decorators
on folders.
>
> When deep-cheking of folders is turned on, they are marked dirty
whenever any
> of its children is dirty.
> And as dirty are also considered unversioned files.
>
> What about a small modification:
>
> - when "select unversioned resources on commit" preference is set ON,
the
> behavior will be unchanged.
> but
> - when "select unversioned resources on commit" preference is set OFF,
then
> those unversioned resources
> will be ignored and the parent folder will NOT be marked as dirty ?
I am just following up on my last post.
Even in the latest trunk I am not seeing unversioned files cause their
parent to be decorated. Are you sure you do not have a prop-change on one
of these folders?
I do not think I would like the idea of this feature. If a dirty
decorator is present, then I would expect the Revert option to always show
me something. In the case of unversioned files, it wouldn't.
On another topic ... I like the new comment headers you are doing for the
license. I just wanted to point out that none of the files have an
@author tag as the comment references. Should we just change the wording
to refer to the repository for author information?
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Sep 29 23:14:50 2005