On 9/13/2012 2:40 PM, Steve Borho wrote:
> On Thu, Sep 13, 2012 at 4:24 PM, Ross Boylan <[email protected]> wrote:
>> I started to write a note about one particular discrepancy I noticed
>> between a menu I saw and the menu in the manual.  It has turned into a
>> long-ish piece on various ways I have trouble figuring out what
>> different functions do, even with the documentation.  My main hope was
>> that this might lead to improved documentation.
>>
>> What would be the most useful way to share that?  Possible responses
>> include "don't bother; nobody is going to update the documentation" (:
>> There is this list, the developer list, the wiki and the bug tracker.
> It's fair to say the documentation is lagging and unloved.
>
> Optimally, you would send us patches to the documentation sources,
> which are in simple text files in Restructured Text format:
> https://bitbucket.org/tortoisehg/thg/src/tip/doc/source
>
> Somewhat less optimal would be an email describing what the text
> should say, this could be patched by someone in a small amount of
> time.
>
> Anything less would have a strong possibility of being quickly forgotten.
>
Bummer.  Unfortunately, I generally couldn't provide patches even if I 
had the time, since to provide a patch I'd have to know what a command 
does, and my problem is I often don't.  I can explain the problem, but 
not solve it.

Ross

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to