<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Makefile, branch v2.11.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.11.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.11.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2016-12-14T17:54:49Z</updated>
<entry>
<title>Makefile: exclude contrib from FIND_SOURCE_FILES</title>
<updated>2016-12-14T17:54:49Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2016-12-14T14:32:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=046e4c1c09aa4fa9865b1fd755aa99d8617465d2'/>
<id>urn:sha1:046e4c1c09aa4fa9865b1fd755aa99d8617465d2</id>
<content type='text'>
When you're working on the git project, you're unlikely to
care about random bits in contrib/ (e.g., you would not want
to jump to the copy of xmalloc in the wincred credential
helper). Nobody has really complained because there are
relatively few C files in contrib.

Now that we're matching shell scripts, too, we get quite a
few more hits, especially in the obsolete contrib/examples
directory. Looking for usage() should turn up the one in
git-sh-setup, not in some long-dead version of git-clone.

Let's just exclude all of contrib. Any specific projects
there which are big enough to want tags can generate them
separately.

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>Makefile: match shell scripts in FIND_SOURCE_FILES</title>
<updated>2016-12-14T17:54:49Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2016-12-14T14:29:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8fa2043293831402b84c3446efa62640c01c8121'/>
<id>urn:sha1:8fa2043293831402b84c3446efa62640c01c8121</id>
<content type='text'>
We feed FIND_SOURCE_FILES to ctags to help developers
navigate to particular functions, but we only feed C source
code. The same feature can be helpful when working with
shell scripts (especially the test suite). Modern versions
of ctags know how to parse shell scripts; we just need to
feed the filenames to it.

This patch specifically avoids including the individual test
scripts themselves. Those are unlikely to be of interest,
and there are a lot of them to process. It does pick up
test-lib.sh and test-lib-functions.sh.

Note that our negative pathspec already excludes the
individual scripts for the ls-files case, but we need to
loosen the `find` rule to match it.

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>Makefile: exclude test cruft from FIND_SOURCE_FILES</title>
<updated>2016-12-14T17:54:49Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2016-12-14T14:28:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e6fc85b11f402ababa4b46ec1121a662ce1fce8e'/>
<id>urn:sha1:e6fc85b11f402ababa4b46ec1121a662ce1fce8e</id>
<content type='text'>
The test directory may contain three types of files that
match our patterns:

  1. Helper programs in t/helper.

  2. Sample data files (e.g., t/t4051/hello.c).

  3. Untracked cruft in trash directories and t/perf/build.

We want to match (1), but not the other two, as they just
clutter up the list.

For the ls-files method, we can drop (2) with a negative
pathspec. We do not have to care about (3), since ls-files
will not list untracked files.

For `find`, we can match both cases with `-prune` patterns.

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>Makefile: reformat FIND_SOURCE_FILES</title>
<updated>2016-12-14T17:54:49Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2016-12-14T14:26:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e951ebca91d914e3fb579011c9218f59c67cf2fd'/>
<id>urn:sha1:e951ebca91d914e3fb579011c9218f59c67cf2fd</id>
<content type='text'>
As we add to this in future commits, the formatting is going
to make it harder and harder to read. Let's write it more as
we would in a shell script, putting each logical block on
its own line.

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 'ls/macos-update'</title>
<updated>2016-11-11T21:56:30Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-11-11T21:56:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=332fd5655a1e162b2fe47009dfc77ca2a94908e7'/>
<id>urn:sha1:332fd5655a1e162b2fe47009dfc77ca2a94908e7</id>
<content type='text'>
Portability update and workaround for builds on recent Mac OS X.

* ls/macos-update:
  travis-ci: disable GIT_TEST_HTTPD for macOS
  Makefile: set NO_OPENSSL on macOS by default
</content>
</entry>
<entry>
<title>Makefile: set NO_OPENSSL on macOS by default</title>
<updated>2016-11-10T19:10:36Z</updated>
<author>
<name>Lars Schneider</name>
<email>larsxschneider@gmail.com</email>
</author>
<published>2016-11-06T19:35:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f01fe92b82be0c3ff1569a2fc719162758bba065'/>
<id>urn:sha1:f01fe92b82be0c3ff1569a2fc719162758bba065</id>
<content type='text'>
Apple removed the OpenSSL header files in macOS 10.11 and above. OpenSSL
was deprecated since macOS 10.7.

Set `NO_OPENSSL` and `APPLE_COMMON_CRYPTO` to `YesPlease` as default for
macOS. It is possible to override this and use OpenSSL by defining
`NO_APPLE_COMMON_CRYPTO`.

Original-patch-by: Torsten Bögershausen &lt;tboegi@web.de&gt;
Signed-off-by: Lars Schneider &lt;larsxschneider@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jk/quarantine-received-objects'</title>
<updated>2016-10-17T20:25:20Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-10-17T20:25:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=25ab004c53cdcfea485e5bf437aeaa74df47196d'/>
<id>urn:sha1:25ab004c53cdcfea485e5bf437aeaa74df47196d</id>
<content type='text'>
In order for the receiving end of "git push" to inspect the
received history and decide to reject the push, the objects sent
from the sending end need to be made available to the hook and
the mechanism for the connectivity check, and this was done
traditionally by storing the objects in the receiving repository
and letting "git gc" to expire it.  Instead, store the newly
received objects in a temporary area, and make them available by
reusing the alternate object store mechanism to them only while we
decide if we accept the check, and once we decide, either migrate
them to the repository or purge them immediately.

* jk/quarantine-received-objects:
  tmp-objdir: do not migrate files starting with '.'
  tmp-objdir: put quarantine information in the environment
  receive-pack: quarantine objects until pre-receive accepts
  tmp-objdir: introduce API for temporary object directories
  check_connected: accept an env argument
</content>
</entry>
<entry>
<title>tmp-objdir: introduce API for temporary object directories</title>
<updated>2016-10-10T20:54:02Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2016-10-03T20:49:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2564d994c9c91aea58d59565d68d42bbc017f536'/>
<id>urn:sha1:2564d994c9c91aea58d59565d68d42bbc017f536</id>
<content type='text'>
Once objects are added to the object database by a process,
they cannot easily be deleted, as we don't know what other
processes may have started referencing them. We have to
clean them up with git-gc, which will apply the usual
reachability and grace-period checks.

This patch provides an alternative: it helps callers create
a temporary directory inside the object directory, and a
temporary environment which can be passed to sub-programs to
ask them to write there (the original object directory
remains accessible as an alternate of the temporary one).

See tmp-objdir.h for details on the API.

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>coccicheck: use --all-includes by default</title>
<updated>2016-09-30T03:40:18Z</updated>
<author>
<name>René Scharfe</name>
<email>l.s.r@web.de</email>
</author>
<published>2016-09-29T23:21:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a9a884aea57b162a3257437b5cbdf8d8037b7c06'/>
<id>urn:sha1:a9a884aea57b162a3257437b5cbdf8d8037b7c06</id>
<content type='text'>
Add a make variable, SPATCH_FLAGS, for specifying flags for spatch, and
set it to --all-includes by default.  This option lets it consider
header files which would otherwise be ignored.  That's important for
some rules that rely on type information.  It doubles the duration of
coccicheck, however.

Signed-off-by: Rene 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 'js/regexec-buf'</title>
<updated>2016-09-26T23:09:19Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-09-26T23:09:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6a67695268562f67babdb7d5195c8a43cc4015fa'/>
<id>urn:sha1:6a67695268562f67babdb7d5195c8a43cc4015fa</id>
<content type='text'>
Some codepaths in "git diff" used regexec(3) on a buffer that was
mmap(2)ed, which may not have a terminating NUL, leading to a read
beyond the end of the mapped region.  This was fixed by introducing
a regexec_buf() helper that takes a &lt;ptr,len&gt; pair with REG_STARTEND
extension.

* js/regexec-buf:
  regex: use regexec_buf()
  regex: add regexec_buf() that can work on a non NUL-terminated string
  regex: -G&lt;pattern&gt; feeds a non NUL-terminated string to regexec() and fails
</content>
</entry>
</feed>
