This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients eric.araujo, orsenthil, r.david.murray
Date 2011-06-20.03:10:04
SpamBayes Score 0.0010885779
Marked as misclassified No
Message-id <1308539405.25.0.235503454169.issue12255@psf.upfronthosting.co.za>
In-reply-to
Content
Well, since there's no central server for hg, it can't track based on the server.  Perhaps I confused you by saying that the .hgignore file was "in the repo".  (It is "in the repo" in the sense that any tracked file is in the repo, but it's effect comes from its existence in the checkout tree from which you are running the hg commands.)

So yes, the .hgignore you get when you clone is so that everybody has the same base list.  That's why we are arguing about its appropriate contents :)
History
Date User Action Args
2011-06-20 03:10:05r.david.murraysetrecipients: + r.david.murray, orsenthil, eric.araujo
2011-06-20 03:10:05r.david.murraysetmessageid: <1308539405.25.0.235503454169.issue12255@psf.upfronthosting.co.za>
2011-06-20 03:10:04r.david.murraylinkissue12255 messages
2011-06-20 03:10:04r.david.murraycreate