mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: "Martin Ågren" <>
Cc: "Bagas Sanjaya" <>,
	"Git Mailing List" <>,
	"Derrick Stolee" <>,
	"Taylor Blau" <>,
	"Dr . Adam Nielsen" <>,
	"Jakub Narębski" <>
Subject: Re: [PATCH 0/3] Documentation: change "folder" to "directory"
Date: Wed, 27 Oct 2021 11:48:04 -0700	[thread overview]
Message-ID: <xmqqh7d2wbh7.fsf@gitster.g> (raw)

Martin Ågren <> writes:

> Old habit, I guess. :) I tend to find that having multiple patches aids
> reviewing. Within reason, obviously. Reviewers don't have to go "I agree
> with everything except that particular hunk", but can just say "I agree
> with everything except patch two", making tracking things a bit easier.

In this case, changes to three separate files are presented in three
separate patches, which was a quite pleasant read.  I do appreciate
that you said "within reason" ;-)

  reply	other threads:[~2021-10-27 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 17:09 [PATCH 0/3] Documentation: change "folder" to "directory" Martin Ågren
2021-10-24 17:09 ` [PATCH 1/3] git-multi-pack-index.txt: " Martin Ågren
2021-10-24 17:09 ` [PATCH 2/3] gitignore.txt: " Martin Ågren
2021-10-24 17:09 ` [PATCH 3/3] gitweb.txt: " Martin Ågren
2021-10-25  9:19 ` [PATCH 0/3] Documentation: " Bagas Sanjaya
2021-10-26  6:02   ` Martin Ågren
2021-10-27 18:48     ` Junio C Hamano [this message]
2021-10-25 15:31 ` Derrick Stolee
2021-10-25 18:08 ` Junio C Hamano

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqh7d2wbh7.fsf@gitster.g \ \ \ \ \ \ \ \ \

* 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

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).