Untrusted hgrc files, why report them?

timeless timeless at gmail.com
Sun Feb 27 06:38:58 CST 2011

On Fri, Feb 25, 2011 at 7:38 PM, Kevin Bullock
<kbullock+mercurial at ringworld.org> wrote:
> Yes, me. It lets me know when I need to add a co-developer to [trusted] in my ~/.hgrc when I clone her/his repo over SSH. :) This is pretty much the only situation in which I've encountered the warning.

i hit it regularly when setting up cross references.

often my web server users don't have home directories, and generally
speaking there isn't anything in the hgrc file that i know of which
qualifies as 'trusted' related.

i'd prefer for the warning to only trigger if mercurial encounters a
flag which would affect the relevant command.

if there's a trigger for push and i do a pull, then i don't care. if
there's a trigger for push and i do a push, then i may care. if
there's a username, and i'm only reading, i almost certainly do not
care. if there's a path and i'm not dealing w/ paths, then i probably
do not care.

tell me about things i need to know when i need to know them. don't
annoy me with information that doesn't affect what i'm doing. i'll
ignore it.

More information about the Mercurial-devel mailing list