<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/remote.c, branch v2.32.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.32.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.32.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2021-03-14T00:00:09Z</updated>
<entry>
<title>use CALLOC_ARRAY</title>
<updated>2021-03-14T00:00:09Z</updated>
<author>
<name>René Scharfe</name>
<email>l.s.r@web.de</email>
</author>
<published>2021-03-13T16:17:22Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ca56dadb4b65ccaeab809d80db80a312dc00941a'/>
<id>urn:sha1:ca56dadb4b65ccaeab809d80db80a312dc00941a</id>
<content type='text'>
Add and apply a semantic patch for converting code that open-codes
CALLOC_ARRAY to use it instead.  It shortens the code and infers the
element size automatically.

Signed-off-by: René Scharfe &lt;l.s.r@web.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'nk/refspecs-negative-fix'</title>
<updated>2020-12-23T21:59:46Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-12-23T21:59:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=73583204d9114b4c86453f5ae74397d9f951072f'/>
<id>urn:sha1:73583204d9114b4c86453f5ae74397d9f951072f</id>
<content type='text'>
Hotfix for recent regression.

* nk/refspecs-negative-fix:
  negative-refspec: improve comment on query_matches_negative_refspec
  negative-refspec: fix segfault on : refspec
</content>
</entry>
<entry>
<title>negative-refspec: improve comment on query_matches_negative_refspec</title>
<updated>2020-12-22T06:49:36Z</updated>
<author>
<name>Nipunn Koorapati</name>
<email>nipunn@dropbox.com</email>
</author>
<published>2020-12-22T03:58:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=773c694142c630ccbf161287b5c2a7ad13e8ca9f'/>
<id>urn:sha1:773c694142c630ccbf161287b5c2a7ad13e8ca9f</id>
<content type='text'>
Comment did not adequately explain how the two loops work
together to achieve the goal of querying for matching of any
negative refspec.

Signed-off-by: Nipunn Koorapati &lt;nipunn@dropbox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>negative-refspec: fix segfault on : refspec</title>
<updated>2020-12-22T06:49:36Z</updated>
<author>
<name>Nipunn Koorapati</name>
<email>nipunn@dropbox.com</email>
</author>
<published>2020-12-22T03:58:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=18f9c9884582c743d8ba04ef5cbbe647947d2578'/>
<id>urn:sha1:18f9c9884582c743d8ba04ef5cbbe647947d2578</id>
<content type='text'>
The logic added to check for negative pathspec match by c0192df630
(refspec: add support for negative refspecs, 2020-09-30) looks at
refspec-&gt;src assuming it is never NULL, however when
remote.origin.push is set to ":", then refspec-&gt;src is NULL,
causing a segfault within strcmp.

Tell git to handle matching refspec by adding the needle to the
set of positively matched refspecs, since matching ":" refspecs
match anything as src.

Add test for matching refspec pushes fetch-negative-refspec
both individually and in combination with a negative refspec.

Signed-off-by: Nipunn Koorapati &lt;nipunn@dropbox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'js/init-defaultbranch-advice'</title>
<updated>2020-12-18T23:15:17Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-12-18T23:15:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=772bdcd4296b259d52aafb0badd79872e9db3bb3'/>
<id>urn:sha1:772bdcd4296b259d52aafb0badd79872e9db3bb3</id>
<content type='text'>
Our users are going to be trained to prepare for future change of
init.defaultBranch configuration variable.

* js/init-defaultbranch-advice:
  init: provide useful advice about init.defaultBranch
  get_default_branch_name(): prepare for showing some advice
  branch -m: allow renaming a yet-unborn branch
  init: document `init.defaultBranch` better
</content>
</entry>
<entry>
<title>Merge branch 'jk/multi-line-indent-style-fix'</title>
<updated>2020-12-14T18:21:38Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-12-14T18:21:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3c9f0df16a20071aa6810152dd7f4003f3d96c4b'/>
<id>urn:sha1:3c9f0df16a20071aa6810152dd7f4003f3d96c4b</id>
<content type='text'>
Style fix.

* jk/multi-line-indent-style-fix:
  style: indent multiline "if" conditions to align
</content>
</entry>
<entry>
<title>get_default_branch_name(): prepare for showing some advice</title>
<updated>2020-12-13T23:53:50Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2020-12-11T11:36:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=cc0f13c57dedaf62c9f852b6bf363aee7e3392f1'/>
<id>urn:sha1:cc0f13c57dedaf62c9f852b6bf363aee7e3392f1</id>
<content type='text'>
We are about to introduce a message giving users running `git init` some
advice about `init.defaultBranch`. This will necessarily be done in
`repo_default_branch_name()`.

Not all code paths want to show that advice, though. In particular, the
`git clone` codepath _specifically_ asks for `init_db()` to be quiet,
via the `INIT_DB_QUIET` flag.

In preparation for showing users above-mentioned advice, let's change
the function signature of `get_default_branch_name()` to accept the
parameter `quiet`.

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>style: indent multiline "if" conditions to align</title>
<updated>2020-12-03T18:32:32Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2020-12-03T08:00:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=08e9df2395b1116ffe932eaedbc3c89676902362'/>
<id>urn:sha1:08e9df2395b1116ffe932eaedbc3c89676902362</id>
<content type='text'>
Commit 6dc905d974 (config: split repo scope to local and worktree,
2020-02-10) made some "if" statements multiline, but didn't indent the
second lines in our usual way.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'sk/force-if-includes'</title>
<updated>2020-10-27T22:09:49Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-10-27T22:09:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=de0a7effc86aadf6177fdcea52b5ae24c7a85911'/>
<id>urn:sha1:de0a7effc86aadf6177fdcea52b5ae24c7a85911</id>
<content type='text'>
"git push --force-with-lease[=&lt;ref&gt;]" can easily be misused to lose
commits unless the user takes good care of their own "git fetch".
A new option "--force-if-includes" attempts to ensure that what is
being force-pushed was created after examining the commit at the
tip of the remote ref that is about to be force-replaced.

* sk/force-if-includes:
  t, doc: update tests, reference for "--force-if-includes"
  push: parse and set flag for "--force-if-includes"
  push: add reflog check for "--force-if-includes"
</content>
</entry>
<entry>
<title>Merge branch 'jk/refspecs-negative'</title>
<updated>2020-10-05T21:01:54Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-10-05T21:01:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8e3ec76a20d6abf5dd8ceb3f5f2c157000e4c13e'/>
<id>urn:sha1:8e3ec76a20d6abf5dd8ceb3f5f2c157000e4c13e</id>
<content type='text'>
"git fetch" and "git push" support negative refspecs.

* jk/refspecs-negative:
  refspec: add support for negative refspecs
</content>
</entry>
</feed>
