Re: [PATCH v2 0/4] Auto-generate mergetool lists
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Jan 28, 2013, 21:01 UTC
- Message-ID
- <2CAD0EB4A81B49E6AAF06BB29A4C8E05@PhilipOakley>
- In-Reply-To
- <CAJDDKr4BT_1YnnfJv-YFHOpWhYpuA_5CMRw_hPTiowMr49RLKQ@mail.gmail.com>
From: "David Aguilar" <davvid@gmail.com> Sent: Monday, January 28, 2013 9:16 AM
Show 22 quoted lines
> On Mon, Jan 28, 2013 at 12:20 AM, Philip Oakley <philipoakley@iee.org> > wrote: >> From: "David Aguilar" <davvid@gmail.com> >> Sent: Monday, January 28, 2013 12:52 AM >> >>> This is round two of this series. >>> I think this touched on everything brought up in the code review. >>> 4/4 could use a review as I'm not completely familiar with the >>> makefile dependencies, though it seems to work correctly. >> >> >> Does this 4/4 have any effect on the Msysgit / Git for Windows >> documentation >> which simply refers [IIRC] to HTML documenation made by Junio? >> >> That is, how easy is it to create a 'default' set of docs, rather >> than >> personalised documenation. Or have I misunderstood how it is working? > > It doesn't have any effect on Msysgit. The resulting documentation > lists all available tools, on all platforms. >
That's useful to know. I must have misunderstood one of the earlier messages suggesting it would also list all the users other (non typical) installed mergetools and hence add them into the documentation.
Philip