Re: [PATCH 3/3] read-cache: don't write index twice if we can't write shared index

From: SZEDER Gábor <szeder.dev@gmail.com>
Date: Jan 22, 2018, 22:10 UTC
Message-ID: <CAM0VKj=EK7ZQkxvhvzyDgKJXxzd19Mtj1vCRULqthVmPj4W2Tg@mail.gmail.com>
In-Reply-To: <CAPig+cQnVfFcN_kH-pQmjJWa_3SeEb4_vdL7-nDCO-tV-U7Pvg@mail.gmail.com>

On Mon, Jan 22, 2018 at 8:46 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:

> On Mon, Jan 22, 2018 at 1:27 PM, SZEDER Gábor <szeder.dev@gmail.com> wrote:

Show 5 quoted lines

>>   - The logs of OSX build jobs have CRCRLF line endings.  However, the
>>     'base64' util of OSX doesn't wrap its output at 76 columns, i.e.
>>     prints one single albeit very long line.  This means that while
>
> Perhaps you could pipe the 'base64' output through 'fold' or 'fmt'?

No need to, according to its manpage[1], OSX's base64 has an option to wrap lines after given number of characters. Of course it uses a different letter for the option than the coreutils base64... :)

(While long lines are ugly, in this particular case it comes handy: when using vim to extract the base64-encoded section from the log to a separate file, it's less keystrokes to yank a single line than to search for the end of the encoded section.)

[1] - https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/base64.1.html