s. If I recall correctly fossil behavior
> is a little odd when it comes to controlled files that match an ignore
> pattern. I seem to remember that a modified controlled file masked by a
> ignore does not show up in "fossil status"
Thanks for the tips, this is the kind of advic
reasonable change, stat, and commit would flag files in the
managed directory tree that aren't managed. Is that helpful or does it
become like the endless Windows OK prompts?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
on to
also provide the oppposite info, letting you know there are new files that
haven't been added.
> To see the list of "unmanaged" files:
>
> fossil extra
Thank you. It is more "manual" than I was looking for but if that's the way
it works that's the w
back do we have to go? When did we break this and when is the
last time it worked? It helps to have a way to compare sections of code over
time...so an annotate in diff form would be invaluable. If this isn't
already available I guess it could be scripted without messing up the fossil
code, even externally scripted.
Thank you for the information and two great products!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
______
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
5 matches
Mail list logo
