On 2017-06-26 10:42, Corinna Vinschen wrote:
> On Jun 26 10:25, Brian Inglis wrote:
>> On 2017-06-26 02:31, Corinna Vinschen wrote:
>>> On Jun 23 12:47, Brian Inglis wrote:
>>>> On 2017-06-23 12:25, Corinna Vinschen wrote:
>>>>> On Jun 23 19:52, Marco Atzeri wrote:
>>>>>> On 22/06/2017 15:58, Corinna Vinschen wrote:
>>>>>>> I uploaded a new Cygwin test release 2.8.1-0.1
>>>>>>> I'm planning for a release next week.  Please test.
>>>>>> $ /etc/postinstall/cygwin-doc.sh
>>>>>> Can't find directory '/usr/share/doc/cygwin-2.8.1'
>>>>> Fixed in git.
>>>>
>>>> Darn you were fast!
>>>> You might want to apply the rest of the attached format-patch,
>>>> as it makes things clearer, more maintainable, and shorter.
>>>
>>> Sure, but your patch doesn't apply cleanly.  Care to check?
>>
>> Refreshed, retried, reattached - not seeing any differences.
> 
> Weird.  See below.
> 
>> Care to give me hint to get a clean format-patch of a changed file against your
>> master?
>> My approach tends to be scorched earth: rm -rf repo && git clone repo!
> 
> `git pull' should suffice...
> 
>> Ramadan is just past, so not a new moon, should I wait to sacrifice more of my
>> hair, to appease git? ;^>
> 
> git am fails because your patch has still the already applied first
> hunk.  If you remove that, and ideally change the subject to match
> what the remaining parts of the patch are doing, it should fly.
Thanks for your patience.
Recloned, recopied from my original, reformated patch attached: hashbang changed
as this script only needs {da,}sh.
Is there an option so git will download your updated source, reject my patched
source in place, and not just overwrite it?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada