On Mon, Jul 2, 2012 at 1:44 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> i'm not personally convinced that an ignore list would completely solve
> the problem (i think that just might lead to more confusion ("i changed the
> file, why isn't it showing as changed?") and corresponding bug reports).
> But it might be a solution or part of a solution. Can you elaborate on how
> you imagine such a feature behaving?
>
Maybe we could have a local list, similar to ignore-glob, like:
fossil forget-local ...list...of...files...
fossil remember-local ...list...of...files... (undoes the forget)
"Forgotten" files would be excluded from commits unless they are explicitly
named on the command-line (as opposed to being in a directory which was
passed on the comment line). Fossil status "should probably" show them as
changed, in any case.
But what happens if the remote is updated? Do those files participate in
merging (i suspect they should)? Are there other corner cases here?
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
