public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.8.1-0.1
Date: Tue, 27 Jun 2017 07:38:00 -0000	[thread overview]
Message-ID: <20170627073835.GN6201@calimero.vinschen.de> (raw)
In-Reply-To: <9893ac7a-7b4a-8eac-fdc2-2d3852c2a5cf@SystematicSw.ab.ca>

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

On Jun 26 13:59, Brian Inglis wrote:
> 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.

Pushed.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2017-06-27  7:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 14:31 Corinna Vinschen
2017-06-23 17:53 ` Marco Atzeri
2017-06-23 18:25   ` Corinna Vinschen
2017-06-23 18:47     ` Brian Inglis
2017-06-26  8:31       ` Corinna Vinschen
2017-06-26 16:25         ` Brian Inglis
2017-06-26 16:42           ` Corinna Vinschen
2017-06-26 20:00             ` Brian Inglis
2017-06-27  1:20               ` Andrey Repin
2017-06-27  5:33                 ` Brian Inglis
2017-06-27  7:56                 ` Corinna Vinschen
2017-06-27 18:53                   ` Brian Inglis
2017-06-27 19:05                     ` Achim Gratz
2017-06-27 20:37                       ` Brian Inglis
2017-06-27  7:38               ` Corinna Vinschen [this message]
2017-06-24  7:35 ` Marco Atzeri
2017-06-26  8:32   ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170627073835.GN6201@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).