From: Leslie Cheng <leslie.cheng5@gmail.com>
To: Eric Wong <e@80x24.org>,
Leslie Cheng via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Leslie Cheng <leslie@lc.fyi>
Subject: Re: [PATCH] Add unix domain socket support to HTTP transport.
Date: Wed, 21 Feb 2024 19:04:38 -0800 [thread overview]
Message-ID: <5a857e76-659d-4d94-ae54-f5c22c9917c6@gmail.com> (raw)
In-Reply-To: <20240221220945.M686016@dcvr>
> No need for trailing `.' in commit message titles
Will fix in the next patch, sorry!
> Personally, I'd hoist the #ifdef part into a standalone function
> since I find mixing CPP and C conditionals confusing.
>
> disclaimer: I'm an easily confused person and don't usually
> program in C, though.
I considered extracting it out, but the other conditionals in this
function follow a similar pattern so I didn't want to change it.
However, my use here is also the first time there's both an #ifdef and
nested #ifndef, which I agree makes it a bit confusing to grok.
I'm open to changing it, but I'll let it sit and marinate for a bit.
> `nc' isn't widely installed, its supported flags vary between
> implementations, and our test suite doesn't currently use it.
> I suggest either using a small bit of Perl or writing a t/helper
> program to do its job.
>
> Finally, hard tabs should be used for indentation throughout.
>
> I'll wait on others to comment since I haven't looked at git
> hacking in a while.
>
> Anyways, I think this feature could be useful for me, too :>
> Thanks.
Good catch, I'll fix in the next patch. I've subbed `nc` out for a
simple Perl script to pipe back and forth, just making sure CI is happy
about this before submitting.
next prev parent reply other threads:[~2024-02-22 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 9:14 [PATCH] Add unix domain socket support to HTTP transport Leslie Cheng via GitGitGadget
2024-02-21 22:09 ` Eric Wong
2024-02-22 3:04 ` Leslie Cheng [this message]
2024-02-23 1:58 ` [PATCH v2] " Leslie Cheng via GitGitGadget
2024-02-23 8:37 ` Junio C Hamano
2024-02-23 15:43 ` Junio C Hamano
2024-02-23 22:24 ` Leslie Cheng
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=5a857e76-659d-4d94-ae54-f5c22c9917c6@gmail.com \
--to=leslie.cheng5@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=leslie@lc.fyi \
/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).