Pulkit Goyal wrote:

> On Sun, May 28, 2017 at 11:30 PM, Augie Fackler <r...@durin42.com> wrote:
> >
> >> On May 26, 2017, at 5:18 PM, Pulkit Goyal <7895pul...@gmail.com> wrote:
> >>
> >> # HG changeset patch
> >> # User Pulkit Goyal <7895pul...@gmail.com>
> >> # Date 1495832891 -19800
> >> #      Sat May 27 02:38:11 2017 +0530
> >> # Node ID 76fb3bdd547259620eec714c0d50fe1f9da25ebf
> >> # Parent  2b5953a49f1407f825d65b45986d213cb5c79203
> >> status: add an option to see terse status (WIP)
> >
> > I’m generally in favor of terse status, but with a quirk: I think it should 
> > only be terse by default for ?, which mirrors the Subversion behavior.
> 
> I was working on this and had a doubt. Shall a folder containing files
> with only unknown and ignored status can be tersed as unknown?

The simple answer to this is yes, if for no other reason than one of the
upsides of terse-status is that it doesn't spend forever descending through
directory hierarchies that have no files managed by mercurial.

If I want to see files there which are ignored, I can always turn off the
terseness, and wait.

Of course, that assumes that the set of ignored files and the set of files
managed by mercurial are exclusive, which they needn't be.  In that case,
I'd probably want to see the ignored files if I simply asked to see ignored
files, even if there were no other managed files in that directory.

So it seems to me that the decision to descend should be made based on
whether there are managed files.

Danek

> An example for this is a folder containing .py and .pyc files from
> which .pyc files are ignored.
> 
> The similar thing applies for modified, and added files. Do we want to
> make all the statuses mutually exclusive to each other while tersing
> OR can some of them exist together and we add the behaviour to use
> --verbose to consider the ignored files. Can we do something else
> also?
> 
> In my opinion the first one will be straightforward for users to
> understand. The later one might result in some confusion.
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel@mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to