From: "Ludovic Courtès" <ludo@gnu.org>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: 50363@debbugs.gnu.org, kyle@kyleam.com, maximedevos@telenet.be
Subject: [bug#50363] [PATCH v4] Improve default diff hunk header detection.
Date: Wed, 22 Sep 2021 14:55:26 +0200 [thread overview]
Message-ID: <87o88khirl.fsf@gnu.org> (raw)
In-Reply-To: <bbac973c0d0388fabe126bd44b60b0683ffe9f03.1632180690.git.iskarian@mgsn.dev> (Sarah Morgensen's message of "Mon, 20 Sep 2021 16:37:44 -0700")
Hi,
Sarah Morgensen <iskarian@mgsn.dev> skribis:
> Tell git where to look for diff hunk headers: top-level definitions for
> Scheme files, and (sub)section headers for texi files.
>
> * .gitattributes, etc/git/gitconfig: New files.
> * doc/contributing.texi ("Submitting Patches"): Add subsection
> "Configuring Git". Document etc/git/gitconfig.
I have one last question:
> +format-patch} sent to the @email{guix-patches@@gnu.org} mailing list
> +(@pxref{submitting patches,, Submitting patches to a project, git, Git
> +User Manual}). Contributors are encouraged to take a moment to set some
AFAICS, there’s no Info-format Git manual, is there? In that case, the
pxref above is incorrect, but we can use @uref instead and/or suggest
‘man git’ or similar.
The rest LGTM, thank you, and thanks Kyle!
Ludo’.
next prev parent reply other threads:[~2021-09-22 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 22:39 [bug#50363] [PATCH v2] Improve default diff hunk header detection Sarah Morgensen
2021-09-10 17:07 ` Maxime Devos
2021-09-13 10:24 ` [bug#50363] [PATCH] " Ludovic Courtès
2021-09-19 18:36 ` [bug#50363] [PATCH v3] " Sarah Morgensen
2021-09-19 22:09 ` Kyle Meyer
2021-09-19 22:56 ` Sarah Morgensen
2021-09-20 0:57 ` Kyle Meyer
2021-09-20 23:37 ` [bug#50363] [PATCH v4] " Sarah Morgensen
2021-09-22 12:55 ` Ludovic Courtès [this message]
2021-09-22 16:22 ` Sarah Morgensen
2021-10-04 12:26 ` bug#50363: [PATCH] " Ludovic Courtès
2021-10-13 22:30 ` [bug#50363] " Marius Bakke
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=87o88khirl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50363@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
--cc=kyle@kyleam.com \
--cc=maximedevos@telenet.be \
/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).