Jonathan Nieder writes:
> Maybe gyp-develo...@googlegroups.com would be the right place. FWIW I
> foolishly tried importing the svn repository into git to write a
> patch, ran into
> http://code.google.com/p/support/issues/detail?id=4647
> and ran out of time.
Ok, I'm busy too so I guess this bu
Timo Juhani Lindfors wrote:
> Jonathan Nieder writes:
>> - See if upstream wants a manpage/HTML manual. If they do, submit it
>>so it can be maintained as part of the upstream package.
>
> That'd be the best option to try first imho. Is upstream bug report
> the way to ask them?
I agree.
Jonathan Nieder writes:
> I tend to despise help2man, at least with most programs' --help output.
> Off the top of my head, here are some other possibilities:
>
> - Combine help2man with po4a to "translate" from --help-ese to
>manpage-ese. This way one gets a nice reminder when the --help
>
Hi,
Timo Juhani Lindfors wrote:
> seems I did some duplication of work since I didn't check the BTS
> before writing a patch to do a very similar fix...
Sorry I missed this.
> The attached patch generates manual page using help2man but adds
> static description, authors and see also sections. D
Hi,
seems I did some duplication of work since I didn't check the BTS
before writing a patch to do a very similar fix...
The attached patch generates manual page using help2man but adds
static description, authors and see also sections. Do you feel that we
could merge these two patches so that do
5 matches
Mail list logo
