zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: PATCH: Allow setting $0 when POSIX_ARGZERO is not set
Date: Tue, 16 Jun 2015 17:12:17 -0700	[thread overview]
Message-ID: <150616171217.ZM28182@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3REzhFCYvLef9pJoVemwD6rmc3AYRNAwfQdV2uFTjgJEQ@mail.gmail.com>

On Jun 17,  1:46am, Mikael Magnusson wrote:
} Subject: Re: PATCH: Allow setting $0 when POSIX_ARGZERO is not set
}
} On Tue, Jun 16, 2015 at 5:58 PM, Bart Schaefer
} <schaefer@brasslantern.com> wrote:
} > On Jun 16,  8:25am, Mikael Magnusson wrote:
} > }
} > } > There are probably other race conditions if a signal were to arrive
} > } > while the shell is still initializing state.  Maybe we should get a
} > } > queue_signals() in there somewhere early.
} > }
} > } Oh, in that case maybe it's a lot more trouble than it's worth...
} >
} > Sorry, the "other race conditions" part has nothing to do with setting
} > argzero, I was merely commenting that if I noticed a race in this part
} > of the initialization code there are probably races elsewhere as well.
} 
} Okay, so it should be fine to push both of the patches in the thread?

I had already committed mine, then had a bit of a problem resolving the
ChangeLog diffs when you pushed 54c2c442eeee46b28d5596e7e83812df01d1f13f
(for which by the way you left out the article number in the commit log
message).

Anyway 35482 is pushed now.


      reply	other threads:[~2015-06-17  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 23:44 Mikael Magnusson
2015-06-16  3:50 ` Bart Schaefer
2015-06-16  6:25   ` Mikael Magnusson
2015-06-16 15:58     ` Bart Schaefer
2015-06-16 23:46       ` Mikael Magnusson
2015-06-17  0:12         ` Bart Schaefer [this message]

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=150616171217.ZM28182@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).