Jiri Sasek wrote:

> Hi Brian,
> 
> IMHO your "fix" will make life more complicated... at least mine
> 
> Currently I am using .hgignore . So immediately I will customize your
> .hgignore to fit into my needs, there will be at least one modified file in
> my workspace.
> 
> So could it be possible to push i.e. "hgignore" to be able to merge it with
> my customizations to ".hgignore".
> 
> I am not a hg-guru so I have 2 processing questions:
> 
>  - is there something like a "post-clone" script which can make some
> customizations in my cloned WS?
>     (i.e.:  cd $hg_root ; cat hgignore ~/my.userland.hgignore > .hgignore)
> 
>  - or is it possible to have "^\.hgignore"-line in .hgignore   ...to ignore
> the .hgignore modifications? (for commit, push, status...)

That's not what .hgignore is used for -- it's used to determine what files
shouldn't be tracked if they're not already.  It's mostly useful when you
"hg add" without a specific file as an argument, or in the output of "hg
status".  It won't make a difference for commit or push, since they've
already been added at that point (it doesn't act, for instance, to populate
-X arguments to commit).

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

Danek
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss

Reply via email to