Hi Yuv,

> .hgignore is global and pushed/pulled across repositories, so
> your .hgignore will go to SourceForge at the next push, and from there
> to me, Harry, and others at our next pull.
>
You are wrong. I did already some commits and my .hgignore did not
gone to sf. Cause: I added also .hgignore to .hgignore
TortoiseHG added the entries to the file. So I assumed, it would be
the right place.

Concerning files going to repository: By using a GUI it is really
straightforward to control which files/changes go into the repository
and which changes remain in the local copy. Therefore I prefer using a
GUI because it allows me finer control about the commits than doing
all on the command line.

> If you want to ignore something on a per-user basis (i.e. locally
> only), you need to reference a file in your ~/.hgrc (or
> <repo>/.hg/.hgrc) file in the "ignore" entry of the [ui] section, e.g.

There is no ~/.hgrc file on windows. It's called mercurial.ini ;-)
But in the repository it's .hg/hgrc (without point). So this setting
stuff is very confusing. Some settings can be changed inside
TortoiseHG (as a global setting and as a repository setting). But the
ignore switch is not included. When I selected to ignore the files,
the .hgignore file was created.

Thomas

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to