<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/contrib, branch 1.2.3</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.2.3</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.2.3'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-02-10T11:48:37Z</updated>
<entry>
<title>Set seekpos to 0 after reopening files in Seek()</title>
<updated>2016-02-10T11:48:37Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-10T11:45:47Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=eda0c1ba43cd3ae0ed85aba2c31573f156cec9c4'/>
<id>urn:sha1:eda0c1ba43cd3ae0ed85aba2c31573f156cec9c4</id>
<content type='text'>
If we just reopened the file, we also need to reset the current
seek position when we reset the buffer, otherwise the code will
not try to seek to the position given to Skip (from 0), but will
try to seek to old offset + the position given to skip.

Closes: #812994, #813000
</content>
</entry>
<entry>
<title>Use some semantically more correct buffer operations</title>
<updated>2016-02-04T17:34:42Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-04T17:33:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=72ed5f14b558984bd9c5731f82345b10cb2df2ca'/>
<id>urn:sha1:72ed5f14b558984bd9c5731f82345b10cb2df2ca</id>
<content type='text'>
When writing into the buffer write to free() bytes starting
at getend(), instead of buffersize_max bytes at get()
-&gt; get() is a read pointer.

This makes no difference in practice though, as we reset
the buffer before the call, so start = end = 0.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>Correctly report write errors when flushing buffered writer</title>
<updated>2016-02-04T17:00:42Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-04T17:00:42Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1996a6a785a54efaeddb4ecf5e88fa6070330182'/>
<id>urn:sha1:1996a6a785a54efaeddb4ecf5e88fa6070330182</id>
<content type='text'>
We cannot just return false without setting an error,
as InternalWrite does not set one itself.
</content>
</entry>
<entry>
<title>Avoid temporary strings in SubstVar.</title>
<updated>2016-02-03T14:54:10Z</updated>
<author>
<name>Adrian Wielgosik</name>
<email>adrian.wielgosik@gmail.com</email>
</author>
<published>2016-02-02T22:15:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=732510fef9af5addc5e3ff1a79ce8c9658711fb6'/>
<id>urn:sha1:732510fef9af5addc5e3ff1a79ce8c9658711fb6</id>
<content type='text'>
Microoptimization, but still gives a measurable 2-3% improvement
when using commands with lots of output like `apt list`.
</content>
</entry>
<entry>
<title>Do not buffer writes larger than the buffer if possible</title>
<updated>2016-02-01T15:50:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-01T15:46:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f1828e6b0adb87bf0b99d3cfeeafbb76cbc6aab7'/>
<id>urn:sha1:f1828e6b0adb87bf0b99d3cfeeafbb76cbc6aab7</id>
<content type='text'>
It makes no sense to split a large block into multiple small
blocks, so when we have the chance to write them unbuffered,
do so.
</content>
</entry>
<entry>
<title>BufferedWriteFileFdPrivate: Simplify InternalWrite()</title>
<updated>2016-02-01T15:29:13Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-01T15:28:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=070ed1c9147c092c1f944afd1c17c51f651a5c39'/>
<id>urn:sha1:070ed1c9147c092c1f944afd1c17c51f651a5c39</id>
<content type='text'>
We do not need the loop, FileFd::Private() handles this for us.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>simple_buffer::write: Use free() instead of maxsize - size()</title>
<updated>2016-02-01T15:25:03Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-01T15:25:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=47fcfff8a50caebe3cd1f2ee19875a2ca8bbeadc'/>
<id>urn:sha1:47fcfff8a50caebe3cd1f2ee19875a2ca8bbeadc</id>
<content type='text'>
We want to check whether the amount of free space is smaller
than the requested write size. Checking maxsize - size() is
incorrect for bufferstart &gt;= 0, as size() = end - start.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>fix "Mismatched free() / delete / delete []" in simple_buffer</title>
<updated>2016-01-30T14:02:42Z</updated>
<author>
<name>Stefan Bühler</name>
<email>stbuehler@web.de</email>
</author>
<published>2016-01-30T11:06:02Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ab16ead7f8e3824f5099558b9d559f6520a24570'/>
<id>urn:sha1:ab16ead7f8e3824f5099558b9d559f6520a24570</id>
<content type='text'>
</content>
</entry>
<entry>
<title>drop explicit check for EWOULDBLOCK if it has the same value as EAGAIN</title>
<updated>2016-01-26T14:32:15Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-01-25T19:05:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3b0e76ec9c9386e428944f621b970d691884b84a'/>
<id>urn:sha1:3b0e76ec9c9386e428944f621b970d691884b84a</id>
<content type='text'>
gcc correctly reports that we check for the same value twice, expect
that the manpage of read(2) tells us to do it for portability, so to
make both sides happy lets add a little #if'ing here.

Reported-By: gcc-6
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>string_view: Drop constexpr constructor for standard compatibility</title>
<updated>2016-01-15T18:18:29Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-01-15T18:18:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ef6cc0e22a2933e0e36bc260179fdf0b86f9ac26'/>
<id>urn:sha1:ef6cc0e22a2933e0e36bc260179fdf0b86f9ac26</id>
<content type='text'>
APT::StringView is supposed to be a temporary measure, until support
for the standardized string_view is widely available. Introducing
additional unstandardized features just makes porting to the
standard version harder.

The constexpr constructor also won't have any real effect on most
systems, as the compiler will happily optimise the strlen() call
away for constant strings.

Gbp-Dch: ignore
</content>
</entry>
</feed>
