From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Andrew Kreimer" <algonell@gmail.com>, git@vger.kernel.org
Cc: "Taylor Blau" <me@ttaylorr.com>
Subject: Re: [PATCH] t1016: clean up style
Date: Sun, 20 Oct 2024 14:46:18 +0200 [thread overview]
Message-ID: <98c5e44f-42c9-47c7-9fa1-e6cc3b35cdb4@app.fastmail.com> (raw)
In-Reply-To: <20241020121729.27032-1-algonell@gmail.com>
Hi
On Sun, Oct 20, 2024, at 14:17, Andrew Kreimer wrote:
> Use `test_config`.
>
> Remove whitespace after redirect operator.
>
> Reported-by: Taylor Blau <me@ttaylorr.com>
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
> ---
> As discussed in:
> - https://lore.kernel.org/git/ZxFyKXDCJkRZYYQY@nand.local/
> […]
> - git config gpg.program $TEST_DIRECTORY/t1016/gpg &&
> - echo "Hellow World!" > hello &&
> + test_config gpg.program $TEST_DIRECTORY/t1016/gpg &&
> + echo "Hellow World!" >hello &&
What Taylor wrote:
> Thanks, both. [Andrew] -- it's fine to do this in the same, or a
> separate patch in the new round. Thanks.
You’ve posted a new, standalone patch. But what Taylor asked for was a
new round on that typo patch where you either squash these changes into
the original patch or have the typo patch plus this one.
At least that’s how I understand it.
This patch by itself doesn’t do much since the file is full of this
style violation. Which I now realize is what you meant when you
asked:[1]
> Do you mean that '> more' and '> another' should be handled similarly?
You were referring to other style violations in the file. But I only
looked at the email so I didn’t catch that.
🔗 1: https://lore.kernel.org/git/ZxKSFBl_pV2r99dY@void.void/
next prev parent reply other threads:[~2024-10-20 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 12:17 [PATCH] t1016: clean up style Andrew Kreimer
2024-10-20 12:46 ` Kristoffer Haugsbakk [this message]
2024-10-21 21:45 ` Taylor Blau
2024-10-21 21:48 ` Taylor Blau
2024-10-22 10:29 ` Andrew Kreimer
-- strict thread matches above, loose matches on Subject: below --
2024-11-02 16:53 Andrew Kreimer
2024-11-02 19:11 ` Kristoffer Haugsbakk
2024-11-03 2:42 ` Junio C Hamano
2024-11-03 13:49 ` Andrew Kreimer
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=98c5e44f-42c9-47c7-9fa1-e6cc3b35cdb4@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=algonell@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
/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;
as well as URLs for NNTP newsgroup(s).