From: Miklos Vajna <vmiklos@frugalware.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dan McGee <dpmcgee@gmail.com>, Eric Hanchrow <offby1@blarg.net>,
git@vger.kernel.org
Subject: Re: generated HTML contains broken links
Date: Sat, 29 Dec 2007 16:57:05 +0100 [thread overview]
Message-ID: <20071229155705.GA23659@genesis.frugalware.org> (raw)
In-Reply-To: <4775B87D.4010507@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Fri, Dec 28, 2007 at 09:01:17PM -0600, Dan McGee <dpmcgee@gmail.com> wrote:
> Generated man pages from Junio:
> HOOKS
> This command can run commit-msg, pre-commit, and post-commit hooks. See
> [1]hooks for more information.
>
> SEE ALSO
> git-add(1), git-rm(1), git-mv(1), git-merge(1), git-commit-tree(1)
>
> AUTHOR
> Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano
> <junkio@cox.net>
>
> GIT
> Part of the git(7) suite
>
> Man pages generated locally (with Asciidoc 8.2.3 or 8.2.5):
> HOOKS
> This command can run commit-msg, pre-commit, and post-commit hooks. See
> hooks[5] for more information.
>
> SEE ALSO
> git1[1], git1[2], git1[8], git1[6], git1[9]
>
> AUTHOR
> Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano
> <junkio@cox.net>
>
> GIT
> Part of the git7[10] suite
http://code.toofishes.net/gitweb.cgi?p=pacman.git;a=commitdiff;h=b3c6bdda38f7e370e1f80f02a61f1d3f08c1b57d
here is the commit that fixed the problem for pacman. what do you think,
should we rename gitlink to something else, too - or should we contact
upstream to notify them about they caused a breakage?
thanks,
- VMiklos
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-29 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 23:49 generated HTML contains broken links Eric Hanchrow
2007-12-29 3:01 ` Dan McGee
2007-12-29 15:57 ` Miklos Vajna [this message]
2007-12-29 16:24 ` Dan McGee
2007-12-29 16:34 ` [PATCH] Documentation: rename gitlink macro to linkgit Dan McGee
2008-01-03 21:01 ` Junio C Hamano
2008-01-04 5:22 ` Yannick Gingras
2008-01-04 5:50 ` Junio C Hamano
2008-01-04 6:11 ` Yannick Gingras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071229155705.GA23659@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=dpmcgee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=offby1@blarg.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).