All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique Soares <henriquegogo@gmail.com>
To: git@vger.kernel.org
Subject: How mantainers check Git diffs and patches?
Date: Wed, 1 Oct 2025 00:30:43 -0300	[thread overview]
Message-ID: <aNygY8Cm7LEaBzV6@localhost> (raw)

Hello,

This is a simple question I have related to the PR diff review process.

How Git maintainers use to check diffs and review the code? I mean,
sometimes I see that there are some large PATCHES that is hard or
probably impossible to review only using e-mail client.

Do you use some syntax highlight in client e-mail; any pipeline that
automatically download e-mails and apply to a local branch; or for each
PR you save the e-mail file then "git apply" to review / test the diff?

This isn't a technical question, I'm just curious about how you do it.

-- Henrique

             reply	other threads:[~2025-10-01  3:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  3:30 Henrique Soares [this message]
2025-10-01  8:15 ` How mantainers check Git diffs and patches? Kristoffer Haugsbakk
2025-10-01 21:12   ` Jeff King
2025-10-02  2:43   ` Henrique Soares
2025-10-01 13:37 ` Konstantin Ryabitsev
2025-10-02  2:59   ` Henrique Soares
2025-10-01 16:41 ` Junio C Hamano
2025-10-02  2:51   ` Henrique Soares
2025-10-02  5:19     ` 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:
  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=aNygY8Cm7LEaBzV6@localhost \
    --to=henriquegogo@gmail.com \
    --cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.