From: Maxime Devos <maximedevos@telenet.be>
To: 55821@debbugs.gnu.org
Subject: bug#55821: contributing: Broken link to Git manual
Date: Mon, 06 Jun 2022 20:22:20 +0200 [thread overview]
Message-ID: <251988a3dc1d603e179dfe47c9de4e05f1396859.camel@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
contributing.texi contains:
@pxref{submitting patches,, Submitting patches to a project, git, Git User Manual}).
However, there is no 'git' info manual. I guess the ', git,' should
be replaced by ',,' or something like that to avoid implying there's
a git info page?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2022-06-06 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 18:22 Maxime Devos [this message]
2022-06-15 20:42 ` bug#55821: contributing: Broken link to Git manual Ludovic Courtès
2022-07-11 19:20 ` Maxim Cournoyer
2022-07-11 21:50 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=251988a3dc1d603e179dfe47c9de4e05f1396859.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55821@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).