From: Junio C Hamano <gitster@pobox.com>
To: "Seija Kijin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Johannes Sixt" <j6t@kdbg.org>,
"Seija Kijin" <doremylover123@gmail.com>
Subject: Re: [PATCH v9 2/2] prep: reformat pthread.c to fit coding guidelines
Date: Fri, 23 Dec 2022 10:51:50 +0900 [thread overview]
Message-ID: <xmqqa63erio9.fsf@gitster.g> (raw)
In-Reply-To: <4c82a16a9950b67416530249157332a6b2afa839.1671729453.git.gitgitgadget@gmail.com> (Seija Kijin via GitGitGadget's message of "Thu, 22 Dec 2022 17:17:33 +0000")
"Seija Kijin via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Subject: Re: [PATCH v9 2/2] prep: reformat pthread.c to fit coding guidelines
I am guessing that you meant to have "prep" stand for "preparation"
(which by the way is not a good thing to have instead of <area>:
prefix). Perhaps "windows-pthread:" or something?
In any case, this step should be done first, i.e. [1/2] of a
two-patch series, as a preparation for the real change, I would
think.
next prev parent reply other threads:[~2022-12-23 1:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 18:34 [PATCH] win32: close handles of threads that have been joined Rose via GitGitGadget
2022-12-19 18:40 ` Ævar Arnfjörð Bjarmason
2022-12-20 7:53 ` Johannes Sixt
2022-12-20 18:57 ` [PATCH v2] " Rose via GitGitGadget
2022-12-20 19:00 ` [PATCH v3] " Rose via GitGitGadget
2022-12-20 20:03 ` [PATCH v4 0/2] " Rose via GitGitGadget
2022-12-20 20:04 ` [PATCH v4 1/2] " Seija Kijin via GitGitGadget
2022-12-20 20:04 ` [PATCH v4 2/2] prep Seija Kijin via GitGitGadget
2022-12-20 21:18 ` [PATCH v5] win32: close handles of threads that have been joined Rose via GitGitGadget
2022-12-20 22:06 ` Johannes Sixt
2022-12-21 4:35 ` [PATCH v6 0/2] " Rose via GitGitGadget
2022-12-21 4:35 ` [PATCH v6 1/2] " Seija Kijin via GitGitGadget
2022-12-21 4:35 ` [PATCH v6 2/2] prep Seija Kijin via GitGitGadget
2022-12-21 4:46 ` [PATCH v7 0/2] win32: close handles of threads that have been joined Rose via GitGitGadget
2022-12-21 4:46 ` [PATCH v7 1/2] " Seija Kijin via GitGitGadget
2022-12-22 7:52 ` Johannes Sixt
2022-12-21 4:46 ` [PATCH v7 2/2] prep Seija Kijin via GitGitGadget
2022-12-22 16:01 ` [PATCH v8] win32: close handles of threads that have been joined Rose via GitGitGadget
2022-12-22 17:17 ` [PATCH v9 0/2] " Rose via GitGitGadget
2022-12-22 17:17 ` [PATCH v9 1/2] " Seija Kijin via GitGitGadget
2022-12-22 17:17 ` [PATCH v9 2/2] prep: reformat pthread.c to fit coding guidelines Seija Kijin via GitGitGadget
2022-12-23 1:51 ` Junio C Hamano [this message]
2022-12-23 19:15 ` [PATCH v10 0/2] win32: close handles of threads that have been joined Rose via GitGitGadget
2022-12-23 19:15 ` [PATCH v10 1/2] win32-pthread: prepare pthread.c for change by formatting Seija Kijin via GitGitGadget
2022-12-23 19:15 ` [PATCH v10 2/2] win32: close handles of threads that have been joined Seija Kijin via GitGitGadget
2022-12-23 19:19 ` [PATCH v11 0/2] " Rose via GitGitGadget
2022-12-23 19:19 ` [PATCH v11 1/2] win32-pthread: prepare pthread.c for change by formatting Seija Kijin via GitGitGadget
2022-12-23 19:19 ` [PATCH v11 2/2] win32: close handles of threads that have been joined Seija Kijin via GitGitGadget
2022-12-24 7:50 ` René Scharfe
2022-12-25 1:40 ` [PATCH v12 0/2] " Rose via GitGitGadget
2022-12-25 1:40 ` [PATCH v12 1/2] win32-pthread: prepare pthread.c for change by formatting Seija Kijin via GitGitGadget
2022-12-26 1:32 ` Junio C Hamano
2022-12-25 1:40 ` [PATCH v12 2/2] win32: close handles of threads that have been joined Seija Kijin via GitGitGadget
2022-12-26 2:07 ` Junio C Hamano
2023-01-03 16:20 ` [PATCH v13 0/2] " Rose via GitGitGadget
2023-01-03 16:20 ` [PATCH v13 1/2] win32: prepare pthread.c for change by formatting Seija Kijin via GitGitGadget
2023-01-03 16:20 ` [PATCH v13 2/2] win32: close handles of threads that have been joined Seija Kijin via GitGitGadget
2023-01-05 15:44 ` [PATCH v14 0/2] " Rose via GitGitGadget
2023-01-05 15:44 ` [PATCH v14 1/2] win32: prepare pthread.c for change by formatting Seija Kijin via GitGitGadget
2023-01-05 15:44 ` [PATCH v14 2/2] win32: close handles of threads that have been joined Seija Kijin via GitGitGadget
2023-01-06 12:28 ` [PATCH v14 0/2] " 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=xmqqa63erio9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=doremylover123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=j6t@kdbg.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 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).