<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Makefile, branch v2.0.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.0.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.0.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2014-06-25T18:47:58Z</updated>
<entry>
<title>Merge branch 'nd/index-pack-one-fd-per-thread' into maint</title>
<updated>2014-06-25T18:47:58Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-06-25T18:47:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a9041df7ab712be1bfad9e6b67bf4cbf0f7c9c9b'/>
<id>urn:sha1:a9041df7ab712be1bfad9e6b67bf4cbf0f7c9c9b</id>
<content type='text'>
We used to disable threaded "git index-pack" on platforms without
thread-safe pread(); use a different workaround for such
platforms to allow threaded "git index-pack".

* nd/index-pack-one-fd-per-thread:
  index-pack: work around thread-unsafe pread()
</content>
</entry>
<entry>
<title>Revert the whole "ask curl-config" topic for now</title>
<updated>2014-04-30T18:00:15Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-04-30T17:58:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b2feb643097a1ec0cbe79fc161f604b6265c049b'/>
<id>urn:sha1:b2feb643097a1ec0cbe79fc161f604b6265c049b</id>
<content type='text'>
Postpone this a bit during the feature freeze and retry the effort
in the next cycle.
</content>
</entry>
<entry>
<title>Merge branch 'db/make-with-curl'</title>
<updated>2014-04-28T22:48:12Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-04-28T22:48:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d8779e1e2536bdd024254af14d2c046bba2bbb01'/>
<id>urn:sha1:d8779e1e2536bdd024254af14d2c046bba2bbb01</id>
<content type='text'>
It turns out that some platforms do ship without curl-config even
though they build with the hardcoded default -lcurl and rely on it
to work.

* db/make-with-curl:
  Makefile: default to -lcurl when no CURL_CONFIG or CURLDIR
</content>
</entry>
<entry>
<title>Makefile: default to -lcurl when no CURL_CONFIG or CURLDIR</title>
<updated>2014-04-28T21:29:14Z</updated>
<author>
<name>Dave Borowitz</name>
<email>dborowitz@google.com</email>
</author>
<published>2014-04-28T21:01:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f3f11fa6a5cee5a90b3ca6a66a25a2beff6996a7'/>
<id>urn:sha1:f3f11fa6a5cee5a90b3ca6a66a25a2beff6996a7</id>
<content type='text'>
The original implementation of CURL_CONFIG support did not match the
original behavior of using -lcurl when CURLDIR was not set. This broke
implementations that were lacking curl-config but did have libcurl
installed along system libraries, such as MSysGit. In other words, the
assumption that curl-config is always installed was incorrect.

Instead, if CURL_CONFIG is empty or returns an empty result (e.g. due
to curl-config being missing), use the old behavior of falling back to
-lcurl.

Signed-off-by: Dave Borowitz &lt;dborowitz@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'db/make-with-curl'</title>
<updated>2014-04-24T19:31:27Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-04-24T19:31:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e42552135a2a396f37053a89f44952ea907870b2'/>
<id>urn:sha1:e42552135a2a396f37053a89f44952ea907870b2</id>
<content type='text'>
Ask curl-config how to link with the curl library, instead of
having only a limited configurability knobs in the Makefile.

* db/make-with-curl:
  Makefile: allow static linking against libcurl
  Makefile: use curl-config to determine curl flags
</content>
</entry>
<entry>
<title>i18n: only extract comments marked with "TRANSLATORS:"</title>
<updated>2014-04-17T18:09:56Z</updated>
<author>
<name>Jiang Xin</name>
<email>worldhello.net@gmail.com</email>
</author>
<published>2014-04-17T05:37:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=47fbfded53d46ef73c5f5c150d6e6e7602a7f66f'/>
<id>urn:sha1:47fbfded53d46ef73c5f5c150d6e6e7602a7f66f</id>
<content type='text'>
When extract l10n messages, we use "--add-comments" option to keep
comments right above the l10n messages for references.  But sometimes
irrelevant comments are also extracted.  For example in the following
code block, the comment in line 2 will be extracted as comment for the
l10n message in line 3, but obviously it's wrong.

        { OPTION_CALLBACK, 0, "ignore-removal", &amp;addremove_explicit,
          NULL /* takes no arguments */,
          N_("ignore paths removed in the working tree (same as
          --no-all)"),
          PARSE_OPT_NOARG, ignore_removal_cb },

Since almost all comments for l10n translators are marked with the same
prefix (tag): "TRANSLATORS:", it's safe to only extract comments with
this special tag.  I.E. it's better to call xgettext as:

        xgettext --add-comments=TRANSLATORS: ...

Also tweaks the multi-line comment in "init-db.c", to make it start with
the proper tag, not "* TRANSLATORS:" (which has a star before the tag).

Signed-off-by: Jiang Xin &lt;worldhello.net@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>index-pack: work around thread-unsafe pread()</title>
<updated>2014-04-16T16:29:41Z</updated>
<author>
<name>Nguyễn Thái Ngọc Duy</name>
<email>pclouds@gmail.com</email>
</author>
<published>2014-03-25T13:41:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=39539495acb24abfb4dee551e3e9f2e696be7abf'/>
<id>urn:sha1:39539495acb24abfb4dee551e3e9f2e696be7abf</id>
<content type='text'>
Multi-threaing of index-pack was disabled with c0f8654
(index-pack: Disable threading on cygwin - 2012-06-26), because
pread() implementations for Cygwin and MSYS were not thread
safe.  Recent Cygwin does offer usable pread() and we enabled
multi-threading with 103d530f (Cygwin 1.7 has thread-safe pread,
2013-07-19).

Work around this problem on platforms with a thread-unsafe
pread() emulation by opening one file handle per thread; it
would prevent parallel pread() on different file handles from
stepping on each other.

Also remove NO_THREAD_SAFE_PREAD that was introduced in c0f8654
because it's no longer used anywhere.

This workaround is unconditional, even for platforms with
thread-safe pread() because the overhead is small (a couple file
handles more) and not worth fragmenting the code.

Signed-off-by: Nguyễn Thái Ngọc Duy &lt;pclouds@gmail.com&gt;
Tested-by: Johannes Sixt &lt;j6t@kdbg.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Makefile: allow static linking against libcurl</title>
<updated>2014-04-15T20:01:51Z</updated>
<author>
<name>Dave Borowitz</name>
<email>dborowitz@google.com</email>
</author>
<published>2014-04-15T10:40:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d5067112db68fcc8c7b13c769c896b17480cb5b0'/>
<id>urn:sha1:d5067112db68fcc8c7b13c769c896b17480cb5b0</id>
<content type='text'>
This requires more flags than can be guessed with the old-style
CURLDIR and related options, so is only supported when curl-config is
present.

Signed-off-by: Dave Borowitz &lt;dborowitz@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Makefile: use curl-config to determine curl flags</title>
<updated>2014-04-15T20:01:49Z</updated>
<author>
<name>Dave Borowitz</name>
<email>dborowitz@google.com</email>
</author>
<published>2014-04-15T10:40:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=61a64fff4f710f43826c8446d3fd8f3ae78c0411'/>
<id>urn:sha1:61a64fff4f710f43826c8446d3fd8f3ae78c0411</id>
<content type='text'>
curl-config should always be installed alongside a curl distribution,
and its purpose is to provide flags for building against libcurl, so
use it instead of guessing flags and dependent libraries.

Allow overriding CURL_CONFIG to a custom path to curl-config, to
compile against a curl installation other than the first in PATH.

Depending on the set of features curl is compiled with, there may be
more libraries required than the previous two options of -lssl and
-lidn. For example, with a vanilla build of libcurl-7.36.0 on Mac OS X
10.9:

$ ~/d/curl-out-7.36.0/lib/curl-config --libs
-L/Users/dborowitz/d/curl-out-7.36.0/lib -lcurl -lgssapi_krb5 -lresolv -lldap -lz

Use this only when CURLDIR is not explicitly specified, to continue
supporting older builds.

Signed-off-by: Dave Borowitz &lt;dborowitz@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jl/nor-or-nand-and'</title>
<updated>2014-04-08T19:00:28Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-04-08T19:00:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d59c12d7ad39f942fc60578ba1e934822f40445b'/>
<id>urn:sha1:d59c12d7ad39f942fc60578ba1e934822f40445b</id>
<content type='text'>
Eradicate mistaken use of "nor" (that is, essentially "nor" used
not in "neither A nor B" ;-)) from in-code comments, command output
strings, and documentations.

* jl/nor-or-nand-and:
  code and test: fix misuses of "nor"
  comments: fix misuses of "nor"
  contrib: fix misuses of "nor"
  Documentation: fix misuses of "nor"
</content>
</entry>
</feed>
