On 06/13/12 18:31, Danek Duvall wrote:
Jiri Sasek wrote:
I have "^\.hgignore" record in my .hgignore to does not report me the
.hgignore in "hg st". So I think if the .hgignore will be added to
repository it will be reported as uncommitted if it will be changed.
Yes; it's been added to the repo, and is no longer an unknown file, so it
will show up as modified if it's been changed.
We could have a convention that local ignore files be called something like
".localignore", and the .hgignore file could ignore that. It's still
require that you add it to your configuration, but then you could keep it
in the repo. Then again, you could always have that file ignore itself.
That said, it would conflict with any .hgignore file you already have. You
can add to it by specifying in your ~/.hgrc, or in your workspace's
.hg/hgrc:
[ui]
ignore = myignorefile
It looks good ...is it also overrides the .hgignore cloned from the
repository?
I don't think it overrides the one checked into the repo, it just augments
it. And, as far as I know, there's no way to put in an anti-ignore
pattern, to ignore the effect of a previous ignore pattern. So it's a bit
limited.
Is there a possibility also to distinguish between i.e. the Userland and
onnv?
Not from a common ignore file. If you use .hg/hgrc, then you can have
[ui]
ignore = $HOME/.hgignore-userland
in the userland gate,
[ui]
ignore = $HOME/.hgignore-on
for your ON gates, etc.
Danek
I'll add .localignore to the .hgignore file as the placeholder. Then the
user can do what they want to create and use it.
--
blu
Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live. - Martin Golding
-----------------------------------------------------------------------|
Brian Utterback - Solaris RPE, Oracle Corporation.
Ph:603-262-3916, Em:[email protected]
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
