<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/CodingGuidelines, branch v2.50.0</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.50.0</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.50.0'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2025-04-14T21:43:53Z</updated>
<entry>
<title>doc: add markup for characters in Guidelines</title>
<updated>2025-04-14T21:43:53Z</updated>
<author>
<name>Jean-Noël Avila</name>
<email>jn.avila@free.fr</email>
</author>
<published>2025-04-12T12:20:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5a5565ec44293869884eb5da2e08bda832616171'/>
<id>urn:sha1:5a5565ec44293869884eb5da2e08bda832616171</id>
<content type='text'>
This rule was already implicitely applied in the converted man pages,
so let's state it loudly.

Signed-off-by: Jean-Noël Avila &lt;jn.avila@free.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>CodingGuidelines: *.txt -&gt; *.adoc fixes</title>
<updated>2025-03-03T21:49:20Z</updated>
<author>
<name>Todd Zullinger</name>
<email>tmz@pobox.com</email>
</author>
<published>2025-03-03T20:44:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7c78c599bb9b51e5cbdae3e7dc1d723eefcf7c61'/>
<id>urn:sha1:7c78c599bb9b51e5cbdae3e7dc1d723eefcf7c61</id>
<content type='text'>
Signed-off-by: Todd Zullinger &lt;tmz@pobox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ps/build'</title>
<updated>2024-12-16T01:54:33Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2024-12-16T01:54:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=29e5596eb8f82015ddb8666079039ae851b8d182'/>
<id>urn:sha1:29e5596eb8f82015ddb8666079039ae851b8d182</id>
<content type='text'>
Build procedure update plus introduction of Meson based builds.

* ps/build: (24 commits)
  Introduce support for the Meson build system
  Documentation: add comparison of build systems
  t: allow overriding build dir
  t: better support for out-of-tree builds
  Documentation: extract script to generate a list of mergetools
  Documentation: teach "cmd-list.perl" about out-of-tree builds
  Documentation: allow sourcing generated includes from separate dir
  Makefile: simplify building of templates
  Makefile: write absolute program path into bin-wrappers
  Makefile: allow "bin-wrappers/" directory to exist
  Makefile: refactor generators to be PWD-independent
  Makefile: extract script to generate gitweb.js
  Makefile: extract script to generate gitweb.cgi
  Makefile: extract script to massage Python scripts
  Makefile: extract script to massage Shell scripts
  Makefile: use "generate-perl.sh" to massage Perl library
  Makefile: extract script to massage Perl scripts
  Makefile: consistently use PERL_PATH
  Makefile: generate doc versions via GIT-VERSION-GEN
  Makefile: generate "git.rc" via GIT-VERSION-GEN
  ...
</content>
</entry>
<entry>
<title>Merge branch 'jc/doc-error-message-guidelines'</title>
<updated>2024-12-13T15:33:37Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2024-12-13T15:33:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5cbe030c866220cc85191cc25e99459d45d9a6ee'/>
<id>urn:sha1:5cbe030c866220cc85191cc25e99459d45d9a6ee</id>
<content type='text'>
Developer documentation update.

* jc/doc-error-message-guidelines:
  CodingGuidelines: a handful of error message guidelines
</content>
</entry>
<entry>
<title>Makefile: allow "bin-wrappers/" directory to exist</title>
<updated>2024-12-06T22:52:11Z</updated>
<author>
<name>Patrick Steinhardt</name>
<email>ps@pks.im</email>
</author>
<published>2024-12-06T13:24:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=95bcd6f0b709ec6e761270732946651757cc11c3'/>
<id>urn:sha1:95bcd6f0b709ec6e761270732946651757cc11c3</id>
<content type='text'>
The "bin-wrappers/" directory gets created by our build system and is
populated with one script for each of our binaries. There isn't anything
inherently wrong with the current layout, but it is somewhat hard to
adapt for out-of-tree build systems.

Adapt the layout such that our "bin-wrappers/" directory always exists
and contains our "wrap-for-bin.sh" script to make things a little bit
easier for subsequent steps.

Signed-off-by: Patrick Steinhardt &lt;ps@pks.im&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>CodingGuidelines: a handful of error message guidelines</title>
<updated>2024-11-29T01:36:06Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2024-11-27T13:23:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=168ebb7159584df425797dd13d8d8986dc08051e'/>
<id>urn:sha1:168ebb7159584df425797dd13d8d8986dc08051e</id>
<content type='text'>
It is more efficient to have something in the coding guidelines
document to point at, when we want to review and comment on a new
message in the codebase to make sure it "fits" in the set of
existing messages.

Let's write down established best practice we are aware of.

Helped-by: Eric Sunshine &lt;sunshine@sunshineco.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>CodingGuidelines: discourage arbitrary suffixes in function names</title>
<updated>2024-10-24T16:51:30Z</updated>
<author>
<name>Karthik Nayak</name>
<email>karthik.188@gmail.com</email>
</author>
<published>2024-10-24T10:53:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=be75cec1b62b9f873c7fc50bbaff3002d82ab458'/>
<id>urn:sha1:be75cec1b62b9f873c7fc50bbaff3002d82ab458</id>
<content type='text'>
We often name functions with arbitrary suffixes like `_1` as an
extension of another existing function. This creates confusion and
doesn't provide good clarity into the functions purpose. Let's document
good function naming etiquette in our CodingGuidelines.

Signed-off-by: Karthik Nayak &lt;karthik.188@gmail.com&gt;
Signed-off-by: Taylor Blau &lt;me@ttaylorr.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ja/doc-synopsis-markup'</title>
<updated>2024-10-10T21:22:24Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2024-10-10T21:22:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=799450316b606d4b6cd5db6a6cc814f1710d923f'/>
<id>urn:sha1:799450316b606d4b6cd5db6a6cc814f1710d923f</id>
<content type='text'>
The way AsciiDoc is used for SYNOPSIS part of the manual pages has
been revamped.  The sources, at least for the simple cases, got
vastly pleasant to work with.

* ja/doc-synopsis-markup:
  doc: apply synopsis simplification on git-clone and git-init
  doc: update the guidelines to reflect the current formatting rules
  doc: introduce a synopsis typesetting
</content>
</entry>
<entry>
<title>doc: update the guidelines to reflect the current formatting rules</title>
<updated>2024-09-24T17:20:25Z</updated>
<author>
<name>Jean-Noël Avila</name>
<email>jn.avila@free.fr</email>
</author>
<published>2024-09-24T07:08:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=029eff9e34fcb622b6eabe9e695fa502a714df4f'/>
<id>urn:sha1:029eff9e34fcb622b6eabe9e695fa502a714df4f</id>
<content type='text'>
Signed-off-by: Jean-Noël Avila &lt;jn.avila@free.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>CodingGuidelines: also mention MAYBE_UNUSED</title>
<updated>2024-08-29T18:28:07Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2024-08-29T18:18:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a051ca5e650138230f3dd61bda911f0f409ebf23'/>
<id>urn:sha1:a051ca5e650138230f3dd61bda911f0f409ebf23</id>
<content type='text'>
A function that uses a parameter in one build may lose all uses of
the parameter in another build, depending on the configuration.  A
workaround for such a case, MAYBE_UNUSED, should also be mentioned
when we recommend the use of UNUSED to our developers.

Keep the addition to the guideline short and document the criteria
to choose between UNUSED and MAYBE_UNUSED near their definition.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
