From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@univ-lyon1.fr>
Cc: COGONI Guillaume <cogoni.guillaume@gmail.com>,
"derrickstolee@github.com" <derrickstolee@github.com>,
"git.jonathan.bressat@gmail.com" <git.jonathan.bressat@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"guillaume.cogoni@gmail.com" <guillaume.cogoni@gmail.com>,
"shaoxuan.yuan02@gmail.com" <shaoxuan.yuan02@gmail.com>
Subject: Re: [PATCH v1 1/1] Documentation/ToolsOnGit.txt: gather information about tools
Date: Sat, 16 Apr 2022 10:11:05 -0700 [thread overview]
Message-ID: <xmqqlew554ye.fsf@gitster.g> (raw)
In-Reply-To: <0f8dbbd6-4d7b-4530-ec85-2eddfcdc9825@univ-lyon1.fr> (Matthieu Moy's message of "Sat, 16 Apr 2022 15:25:39 +0200")
Matthieu Moy <Matthieu.Moy@univ-lyon1.fr> writes:
> Actually, the Linux kernel's CodingStyle contains more relevant stuff
> (for C, not Perl):
True.
> https://www.kernel.org/doc/html/v4.10/process/coding-style.html#you-ve-made-a-mess-of-it
>
> (But aren't all Git devs former kernel developers? ;-) )
It's 2022, Matthieu, not 2005 ;-).
Thanks for a helpful and useful review.
next prev parent reply other threads:[~2022-04-16 17:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 20:25 [PATCH 0/1] documentation: guide of best practices for GIT developer COGONI Guillaume
2022-04-12 20:25 ` [PATCH 1/1] " COGONI Guillaume
2022-04-13 14:36 ` [PATCH 0/1] " Shaoxuan Yuan
2022-04-13 16:36 ` Guillaume Cogoni
2022-04-16 12:34 ` [PATCH v1 0/1] Documentation/ToolsOnGit.txt: gather information about tools COGONI Guillaume
2022-04-16 12:34 ` [PATCH v1 1/1] " COGONI Guillaume
[not found] ` <63d7dc69656e47f7bc7bce4839711f32@SAMBXP02.univ-lyon1.fr>
2022-04-16 13:25 ` Matthieu Moy
2022-04-16 14:51 ` Philip Oakley
2022-04-16 17:11 ` Junio C Hamano [this message]
2022-04-17 9:35 ` [PATCH v2 0/1] Documentation/ToolsForGit.txt: Tools for developing Git COGONI Guillaume
2022-04-17 9:35 ` [PATCH v2 1/1] " COGONI Guillaume
[not found] ` <33d2087c66e44037b03db818dae60fea@SAMBXP02.univ-lyon1.fr>
2022-04-17 12:25 ` [PATCH v2 0/1] " Matthieu Moy
2022-04-20 13:06 ` [PATCH v3 " COGONI Guillaume
2022-04-20 13:06 ` [PATCH v3 1/1] " COGONI Guillaume
2022-04-20 21:23 ` Junio C Hamano
2022-04-21 8:45 ` [PATCH v4 0/1] " COGONI Guillaume
2022-04-21 8:45 ` [PATCH v4 1/1] " COGONI Guillaume
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=xmqqlew554ye.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@univ-lyon1.fr \
--cc=cogoni.guillaume@gmail.com \
--cc=derrickstolee@github.com \
--cc=git.jonathan.bressat@gmail.com \
--cc=git@vger.kernel.org \
--cc=guillaume.cogoni@gmail.com \
--cc=shaoxuan.yuan02@gmail.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 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.