Git development
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Harald Nordgren <haraldnordgren@gmail.com>, phillip.wood@dunelm.org.uk
Cc: Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,
	Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: [PATCH] status: compare against both upstream and push branch by default
Date: Tue, 20 Oct 2026 14:22:35 +0100	[thread overview]
Message-ID: <a5fa416c-da26-4f7d-8a66-3dd11ed7937c@gmail.com> (raw)
In-Reply-To: <CAHwyqnU1NPp3N7Qv3ChEPCo-mL=gASeG334YFg2tczzLomsm6A@mail.gmail.com>

On 20/10/2026 11:19, Harald Nordgren wrote:
> 
> As a side note:
> 
> I see that you include the whole message in replies, leaving
> responders to clean it, so more work for multiple people instead of
> more work for a single person. Isn't the convention to only include
> the parts that you are responding to?
I tend not to trim the message below my signature (which indicates the 
end of my comments), but I do trim the context above it. I aim to leave 
enough context that someone reading my reply can comprehend it without 
needing to read the message I'm replying to. In this case the original 
commit message was only a couple of paragraphs and I though it was 
relevant context for my reply so I left it in. As a thread gets longer 
I'll trim earlier discussions more aggressively.

Thanks

Phillip

      parent reply	other threads:[~2026-10-20 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 19:23 [PATCH] status: compare against both upstream and push branch by default Harald Nordgren via GitGitGadget
2026-10-19 22:54 ` Junio C Hamano
2026-10-20  9:16   ` Harald Nordgren
2026-10-20  9:33 ` Phillip Wood
2026-10-20 10:19   ` Harald Nordgren
2026-10-20 10:56     ` Kristoffer Haugsbakk
2026-10-20 13:22     ` Phillip Wood [this message]

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=a5fa416c-da26-4f7d-8a66-3dd11ed7937c@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=haraldnordgren@gmail.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    /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