<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/README.md, branch v2.40.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.40.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.40.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2022-02-09T22:20:59Z</updated>
<entry>
<title>Merge branch 'po/readme-mention-contributor-hints'</title>
<updated>2022-02-09T22:20:59Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2022-02-09T22:20:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2981dbea7894bf3d512263ac47ac84af8e1433b2'/>
<id>urn:sha1:2981dbea7894bf3d512263ac47ac84af8e1433b2</id>
<content type='text'>
Doc update.

* po/readme-mention-contributor-hints:
  README.md: add CodingGuidelines and a link for Translators
</content>
</entry>
<entry>
<title>README.md: add CodingGuidelines and a link for Translators</title>
<updated>2022-01-17T19:43:14Z</updated>
<author>
<name>Philip Oakley</name>
<email>philipoakley@iee.email</email>
</author>
<published>2022-01-17T18:18:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4ed7dfa7135385d29bc09358d0b1d373a7ef7c0e'/>
<id>urn:sha1:4ed7dfa7135385d29bc09358d0b1d373a7ef7c0e</id>
<content type='text'>
Before being told how to submit patches, new contributors need
to be told how to code for, or how to contribute translation to,
the project.  Add references to the CodingGuidelines and the
README document on localization.

Also, split out the instructions to join the list and clarify
that subscription is via the majordomo address.

We use GitHub Markdown reference [2,3] with trailing empty square
brackets, to match existing text in the file.  On GitHub/GitLab
pages, the footer references matching the empty [] are not shown
on the web page. We could switch to using [text](url) form [1]
if we wanted to, but that is not done as part of this patch.

[1] https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links
[2] https://gist.github.com/ChrisTollefson/a3af6d902a74a0afd1c2d79aadc9bb3f#reference-links
[3] https://github.github.com/gfm/#example-561 (and the para aboveit)

Signed-off-by: Philip Oakley &lt;philipoakley@iee.email&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>CI: use shorter names that fit in UX tooltips</title>
<updated>2021-11-24T00:51:53Z</updated>
<author>
<name>Ævar Arnfjörð Bjarmason</name>
<email>avarab@gmail.com</email>
</author>
<published>2021-11-23T16:29:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=df7375d77287f3665867b99ae18fc3cbe3289a67'/>
<id>urn:sha1:df7375d77287f3665867b99ae18fc3cbe3289a67</id>
<content type='text'>
Change the names used for the GitHub CI workflows to be short enough
to (mostly) fit in the pop-up tool-tips that GitHub shows in the
commit view. I.e. when mouse-clicking on the passing or failing
check-mark next to the commit subject.

These names are seemingly truncated to 17-20 characters followed by
three dots ("..."). Since a "CI/PR / " prefix is added to them the job
names looked like this before (windows-test and vs-test jobs omitted):

    CI/PR / ci-config (p...
    CI/PR / windows-buil...
    CI/PR / vs-build (pu...
    CI/PR / regular (lin...
    CI/PR / regular (lin...
    CI/PR / regular (os...
    CI/PR / regular (os...
    CI/PR / regular (lin...
    CI/PR / regular (lin...
    CI/PR / dockerized (...
    CI/PR / dockerized (...
    CI/PR / dockerized (...
    CI/PR / static-anal...
    CI/PR / sparse (pu...
    CI/PR / documenta...

By omitting the "/PR" from the top-level name, and pushing the
$jobname to the front we'll now instead get:

    CI / config (push)
    CI / win build (push...
    CI / win+VS build (...
    CI / linux-clang (ub...
    CI / linux-gcc (ubun...
    CI / osx-clang (osx)...
    CI / osx-gcc (osx) (...
    CI / linux-gcc-defau...
    CI / linux-leaks (ub...
    CI / linux-musl (alp...
    CI / Linux32 (daald/...
    CI / pedantic (fedor...
    CI / static-analysis...
    CI / sparse (push)...
    CI / documentation

We then have no truncation in the expanded view. See [1] for how it
looked before, [2] for a currently visible CI run using this commit,
and [3] for the GitHub workflow syntax involved being changed here.

Let's also use the existing "pool" field as before. It's occasionally
useful to know we're running on say ubuntu v.s. fedora. The "-latest"
suffix is useful to some[4], and since it's now at the end it doesn't
hurt readability in the short view compared to saying "ubuntu" or
"macos".

1. https://github.com/git/git/tree/master/
2. https://github.com/avar/git/tree/avar/ci-rm-travis-cleanup-ci-names-3
3. https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions
3. https://lore.kernel.org/git/d9b07ca5-b58d-a535-d25b-85d7f12e6295@github.com/

Signed-off-by: Ævar Arnfjörð Bjarmason &lt;avarab@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>ci: retire the Azure Pipelines definition</title>
<updated>2020-04-10T17:30:40Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2020-04-10T17:18:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6081d3898fe5e33e739cc0771f6df102b30b1db6'/>
<id>urn:sha1:6081d3898fe5e33e739cc0771f6df102b30b1db6</id>
<content type='text'>
We have GitHub Actions now. Running the same builds and tests in Azure
Pipelines would be redundant, and a waste of energy.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Đoàn Trần Công Danh &lt;congdanhqx@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README: add a build badge for the GitHub Actions runs</title>
<updated>2020-04-10T17:30:40Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2020-04-10T17:18:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9ae7dcb40252c173dbd57621a342d0bebb317e21'/>
<id>urn:sha1:9ae7dcb40252c173dbd57621a342d0bebb317e21</id>
<content type='text'>
Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Đoàn Trần Công Danh &lt;congdanhqx@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>doc: recommend lore.kernel.org over public-inbox.org</title>
<updated>2019-11-30T17:12:04Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2019-11-27T12:53:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=46c67492aa3ab2779f9322790ca8fffcd5bfaa80'/>
<id>urn:sha1:46c67492aa3ab2779f9322790ca8fffcd5bfaa80</id>
<content type='text'>
Since lore.kernel.org now has the same archive as public-inbox.org and
may have more longevity going forward[1], let's recommend people use it
for finding or referencing messages.

[1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/
      or if you like:
    https://lore.kernel.org/git/20191120195556.GA25189@dcvr/

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Acked-by: Eric Wong &lt;e@80x24.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README: fix rendering of text in angle brackets</title>
<updated>2019-07-18T21:47:46Z</updated>
<author>
<name>Doug Ilijev</name>
<email>doug.ilijev@gmail.com</email>
</author>
<published>2019-07-18T19:08:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7926cee90466f3fcc3120b2d532c831474d5c2e7'/>
<id>urn:sha1:7926cee90466f3fcc3120b2d532c831474d5c2e7</id>
<content type='text'>
Markdown incorrectly interpreted `&lt;commandname&gt;` as an HTML tag;
use backticks to escape `Documentation/git-&lt;commandname&gt;.txt` to ensure
that it renders the text as intended.

Signed-off-by: Doug Ilijev &lt;doug.ilijev@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README: adjust for final Azure Pipeline ID</title>
<updated>2019-02-24T05:27:04Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2019-02-23T14:49:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=39ffebd23b1ef6830bf86043ef0b5c069d9299a9'/>
<id>urn:sha1:39ffebd23b1ef6830bf86043ef0b5c069d9299a9</id>
<content type='text'>
During the six months of development of the Azure Pipelines support, the
patches went through quite a few iterations of changes, and to test
those iterations, a temporary build definition was used.

In the meantime, Azure Pipelines support made it to `master`, and we now
have a regular Azure Pipeline, installed via the common GitHub App
workflow. This new pipeline has a different name (git.git instead of
test-git.git), and a new ID (11 instead of 2).

Let's adjust the badge in our README to reflect that final shape of the
Azure Pipeline.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README: add a build badge (status of the Azure Pipelines build)</title>
<updated>2019-01-29T17:26:47Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2019-01-29T14:19:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5f7864663bdb71635b4aaf0d996db14e4d521ff6'/>
<id>urn:sha1:5f7864663bdb71635b4aaf0d996db14e4d521ff6</id>
<content type='text'>
Just like so many other OSS projects, we now also have a build badge.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>note git-security@googlegroups.com in more places</title>
<updated>2018-06-01T00:24:11Z</updated>
<author>
<name>Thomas Gummerer</name>
<email>t.gummerer@gmail.com</email>
</author>
<published>2018-05-30T20:52:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2a00502b14cd88299c8e69abcedf8aadcfaaaa6e'/>
<id>urn:sha1:2a00502b14cd88299c8e69abcedf8aadcfaaaa6e</id>
<content type='text'>
Add a mention of the security mailing list to the README, and to
Documentation/SubmittingPatches..  2caa7b8d27 ("git manpage: note
git-security@googlegroups.com", 2018-03-08) already added it to the
man page, but for developers either the README, or the documentation
on how to contribute (SubmittingPatches) may be the first place to
look.

Use the same wording as we already have on the git-scm.com website and
in the man page for the README, while the wording is adjusted in
SubmittingPatches to match the surrounding document better.

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