All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Subject: [OSSTEST PATCH 0/4] Use ^ for negation, not !
Date: Thu, 3 May 2018 15:58:11 +0100	[thread overview]
Message-ID: <1525359495-30844-1-git-send-email-ian.jackson@eu.citrix.com> (raw)

People keep having trouble with the ! syntax for negation, because of
the !-history feature in some shells (notably, enabled by default in
bash in all distros).

The result is that attempts to deallocate hosts, or do some other
things, produces an incomprensible "event not found" message.

I don't suffer from this because I have it turned off, with set -H.
IMO it should be off by default.  (This is Debian #897422.)

Avoid this whole problem by using ^ everywhere we previously used !
for negation.  (We continue to honour !.)

Places where ! is still the necessary syntactic character to do
something in osstest are:

 * In the ms-queuedaemon protocol, ! is used to indicate an
   unsolicited response.

 * In sg-run-job, ! in an IFFAIL means to run a step even if
   the job has failed or is being truncated.

These go nowhere near a shell and are not, conceptually, negation.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2018-05-03 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 14:58 Ian Jackson [this message]
2018-05-03 14:58 ` [OSSTEST PATCH 1/4] mg-allocate: Use ^ for deallocation, not ! Ian Jackson
2018-05-03 14:58 ` [OSSTEST PATCH 2/4] mg-hosts: Use ^ for flag negation, " Ian Jackson
2018-05-03 14:58 ` [OSSTEST PATCH 3/4] mg-adjust-flight-makexrefs: Use ^ for excluding jobs, " Ian Jackson
2018-05-03 14:58 ` [OSSTEST PATCH 4/4] Standalone HostFlags: Use ^ for negation, " Ian Jackson

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=1525359495-30844-1-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.