Skip to content

Commit 6ca5372

Browse files
gitstergitster
committed
Autogenerated HTML docs for v2.45.1-410-g58bac4
1 parent 1bfbb6c commit 6ca5372

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

51 files changed

+1042
-106
lines changed

‎DecisionMaking.html

Lines changed: 821 additions & 0 deletions
Large diffs are not rendered by default.

‎DecisionMaking.txt

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
Decision-Making Process in the Git Project
2+
==========================================
3+
4+
Introduction
5+
------------
6+
This document describes the current decision-making process in the Git
7+
project. It is a descriptive rather than prescriptive doc; that is, we want to
8+
describe how things work in practice rather than explicitly recommending any
9+
particular process or changes to the current process.
10+
11+
Here we document how the project makes decisions for discussions
12+
(with or without patches), in scale larger than an individual patch
13+
series (which is fully covered by the SubmittingPatches document).
14+
15+
16+
Larger Discussions (with patches)
17+
---------------------------------
18+
As with discussions on an individual patch series, starting a larger-scale
19+
discussion often begins by sending a patch or series to the list. This might
20+
take the form of an initial design doc, with implementation following in later
21+
iterations of the series (for example,
22+
link:https://lore.kernel.org/git/0169ce6fb9ccafc089b74ae406db0d1a8ff8ac65.1688165272.git.steadmon@google.com/[adding unit tests] or
23+
link:https://lore.kernel.org/git/20200420235310.94493-1-emilyshaffer@google.com/[config-based hooks]),
24+
or it might include a full implementation from the beginning.
25+
In either case, discussion progresses the same way for an individual patch series,
26+
until consensus is reached or the topic is dropped.
27+
28+
29+
Larger Discussions (without patches)
30+
------------------------------------
31+
Occasionally, larger discussions might occur without an associated patch series.
32+
These may be very large-scale technical decisions that are beyond the scope of
33+
even a single large patch series, or they may be more open-ended,
34+
policy-oriented discussions (examples:
35+
link:https://lore.kernel.org/git/ZZ77NQkSuiRxRDwt@nand.local/[introducing Rust]
36+
or link:https://lore.kernel.org/git/YHofmWcIAidkvJiD@google.com/[improving submodule UX]).
37+
In either case, discussion progresses as described above for general patch series.
38+
39+
For larger discussions without a patch series or other concrete implementation,
40+
it may be hard to judge when consensus has been reached, as there are not any
41+
official guidelines. If discussion stalls at this point, it may be helpful to
42+
restart discussion with an RFC patch series (such as a partial, unfinished
43+
implementation or proof of concept) that can be more easily debated.
44+
45+
When consensus is reached that it is a good idea, the original
46+
proposer is expected to coordinate the effort to make it happen,
47+
with help from others who were involved in the discussion, as
48+
needed.
49+
50+
For decisions that require code changes, it is often the case that the original
51+
proposer will follow up with a patch series, although it is also common for
52+
other interested parties to provide an implementation (or parts of the
53+
implementation, for very large changes).
54+
55+
For non-technical decisions such as community norms or processes, it is up to
56+
the community as a whole to implement and sustain agreed-upon changes.
57+
The project leadership committe (PLC) may help the implementation of
58+
policy decisions.
59+
60+
61+
Other Discussion Venues
62+
-----------------------
63+
Occasionally decision proposals are presented off-list, e.g. at the semi-regular
64+
Contributors' Summit. While higher-bandwidth face-to-face discussion is often
65+
useful for quickly reaching consensus among attendees, generally we expect to
66+
summarize the discussion in notes that can later be presented on-list. For an
67+
example, see the thread
68+
link:https://lore.kernel.org/git/AC2EB721-2979-43FD-922D-C5076A57F24B@jramsay.com.au/[Notes
69+
from Git Contributor Summit, Los Angeles (April 5, 2020)] by James Ramsay.
70+
71+
We prefer that "official" discussion happens on the list so that the full
72+
community has opportunity to engage in discussion. This also means that the
73+
mailing list archives contain a more-or-less complete history of project
74+
discussions and decisions.

‎MyFirstContribution.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -735,7 +735,7 @@
735735
<body class="article">
736736
<div id="header">
737737
<h1>My First Contribution to the Git Project</h1>
738-
<span id="revdate">2024-05-28</span>
738+
<span id="revdate">2024-05-30</span>
739739
</div>
740740
<div id="content">
741741
<div class="sect1">

‎MyFirstObjectWalk.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -735,7 +735,7 @@
735735
<body class="article">
736736
<div id="header">
737737
<h1>My First Object Walk</h1>
738-
<span id="revdate">2024-05-28</span>
738+
<span id="revdate">2024-05-30</span>
739739
</div>
740740
<div id="content">
741741
<div class="sect1">

‎RelNotes/2.46.0.txt

Lines changed: 25 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,9 @@ UI, Workflows & Features
4949
to the recent update to "git config" that adopted subcommand based
5050
UI.
5151

52+
* The knobs to tweak how reftable files are written have been made
53+
available as configuration variables.
54+
5255

5356
Performance, Internal Implementation, Development Support etc.
5457

@@ -87,14 +90,24 @@ Performance, Internal Implementation, Development Support etc.
8790
builtin/config.c done via the use of global variables.
8891

8992
* The pack bitmap code saw some clean-up to prepare for a follow-up topic.
90-
(merge 85f360fee5 tb/pack-bitmap-write-cleanups later to maint).
9193

9294
* Preliminary code clean-up for "git send-email".
93-
(merge c02dc38570 ds/send-email-per-message-block later to maint).
9495

9596
* The default "creation-factor" used by "git format-patch" has been
9697
raised to make it more aggressively find matching commits.
97-
(merge c22d41d641 jc/format-patch-more-aggressive-range-diff later to maint).
98+
99+
* Before discovering the repository details, We used to assume SHA-1
100+
as the "default" hash function, which has been corrected. Hopefully
101+
this will smoke out codepaths that rely on such an unwarranted
102+
assumptions.
103+
104+
* The project decision making policy has been documented.
105+
106+
* The strcmp-offset tests have been rewritten using the unit test
107+
framework.
108+
109+
* "git add -p" learned to complain when an answer with more than one
110+
letter is given to a prompt that expects a single letter answer.
98111

99112

100113
Fixes since v2.45
@@ -180,6 +193,15 @@ Fixes since v2.45
180193
the keychain.
181194
(merge e1ab45b2da kn/osxkeychain-skip-idempotent-store later to maint).
182195

196+
* The chainlint script (invoked during "make test") did nothing when
197+
it failed to detect the number of available CPUs. It now falls
198+
back to 1 CPU to avoid the problem.
199+
(merge 2e7e9205be es/chainlint-ncores-fix later to maint).
200+
201+
* Revert overly aggressive "layered defence" that went into 2.45.1
202+
and friends, which broke "git-lfs", "git-annex", and other use
203+
cases, so that we can rebuild necessary counterparts in the open.
204+
183205
* Other code cleanup, docfix, build fix, etc.
184206
(merge 4cf6e7bf5e jt/doc-submitting-rerolled-series later to maint).
185207
(merge a5a4cb7b27 rs/diff-parseopts-cleanup later to maint).

‎ReviewingGuidelines.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -735,7 +735,7 @@
735735
<body class="article">
736736
<div id="header">
737737
<h1>Reviewing Patches in the Git Project</h1>
738-
<span id="revdate">2024-05-28</span>
738+
<span id="revdate">2024-05-30</span>
739739
</div>
740740
<div id="content">
741741
<div class="sect1">

‎SubmittingPatches.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -735,7 +735,7 @@
735735
<body class="article">
736736
<div id="header">
737737
<h1>Submitting Patches</h1>
738-
<span id="revdate">2024-05-28</span>
738+
<span id="revdate">2024-05-30</span>
739739
</div>
740740
<div id="content">
741741
<div class="sect1">

‎ToolsForGit.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -735,7 +735,7 @@
735735
<body class="article">
736736
<div id="header">
737737
<h1>Tools for developing Git</h1>
738-
<span id="revdate">2024-05-28</span>
738+
<span id="revdate">2024-05-30</span>
739739
</div>
740740
<div id="content">
741741
<div class="sect1">

‎config.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -498,6 +498,8 @@ include::config/rebase.txt[]
498498

499499
include::config/receive.txt[]
500500

501+
include::config/reftable.txt[]
502+
501503
include::config/remote.txt[]
502504

503505
include::config/remotes.txt[]

‎everyday.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -735,7 +735,7 @@
735735
<body class="article">
736736
<div id="header">
737737
<h1>Everyday Git With 20 Commands Or So</h1>
738-
<span id="revdate">2024-05-28</span>
738+
<span id="revdate">2024-05-30</span>
739739
</div>
740740
<div id="content">
741741
<div id="preamble">

0 commit comments

Comments
 (0)