All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Cleber Rosa <crosa@redhat.com>
Cc: Nir Soffer <nsoffer@redhat.com>,
	qemu-block <qemu-block@nongnu.org>,
	qemu-trivial@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH v2 1/4] qemu-iotests: remove bash shebang from library files
Date: Fri, 11 Oct 2019 22:30:46 +0200	[thread overview]
Message-ID: <20191011203046.GI5158@localhost.localdomain> (raw)
In-Reply-To: <20191011200501.GA18783@dhcp-17-179.bos.redhat.com>

Am 11.10.2019 um 22:05 hat Cleber Rosa geschrieben:
> On Fri, Oct 11, 2019 at 02:27:25PM +0300, Nir Soffer wrote:
> > On Fri, Oct 11, 2019, 12:36 Kevin Wolf <kwolf@redhat.com> wrote:
> > 
> > > Am 09.10.2019 um 21:47 hat Cleber Rosa geschrieben:
> > > > Due to not being able to find a reason to have shebangs on files that
> > > > are not executable.
> > > >
> > > > While at it, add a mode hint to emacs, which would be clueless or
> > > > plain wrong about these containing shell code.
> > >
> > > vim still doesn't like the change.
> > >
> > > Of course, we could also add another line for vim and for every other
> > > editor in use, but actually, I think I'd prefer just dropping this
> > > patch. It even makes each file a few bytes larger instead of saving
> > > something. Shebang lines are a shorter and more portable format
> > > indicator than the alternatives.
> > >
> > > So I think in the end we have found a good reason to keep them. :-)
> > 
> > What about .sh suffix? Should be most portable way.
> 
> That's the approach I tend to follow for my sh code.  Explicit is
> better than implicit if you ask me.

I would certainly agree for new files.

> Kevin,
> 
> Do you have any strong feelings here?  I'd be fine with either this
> or dropping the patch.

No strong feelings. The result of renaming the files would be a bit
nicer than what we have today, but renaming always comes with a cost
when working with the version history later. Hard to tell if it's a net
gain or loss in the end.

Myself, I would probably pick the lazy way and stick with "if it ain't
broke, don't fix it", but I'm not objecting to a change either.

Kevin


WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: Cleber Rosa <crosa@redhat.com>
Cc: qemu-block <qemu-block@nongnu.org>,
	qemu-trivial@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>,
	Nir Soffer <nsoffer@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH v2 1/4] qemu-iotests: remove bash shebang from library files
Date: Fri, 11 Oct 2019 22:30:46 +0200	[thread overview]
Message-ID: <20191011203046.GI5158@localhost.localdomain> (raw)
In-Reply-To: <20191011200501.GA18783@dhcp-17-179.bos.redhat.com>

Am 11.10.2019 um 22:05 hat Cleber Rosa geschrieben:
> On Fri, Oct 11, 2019 at 02:27:25PM +0300, Nir Soffer wrote:
> > On Fri, Oct 11, 2019, 12:36 Kevin Wolf <kwolf@redhat.com> wrote:
> > 
> > > Am 09.10.2019 um 21:47 hat Cleber Rosa geschrieben:
> > > > Due to not being able to find a reason to have shebangs on files that
> > > > are not executable.
> > > >
> > > > While at it, add a mode hint to emacs, which would be clueless or
> > > > plain wrong about these containing shell code.
> > >
> > > vim still doesn't like the change.
> > >
> > > Of course, we could also add another line for vim and for every other
> > > editor in use, but actually, I think I'd prefer just dropping this
> > > patch. It even makes each file a few bytes larger instead of saving
> > > something. Shebang lines are a shorter and more portable format
> > > indicator than the alternatives.
> > >
> > > So I think in the end we have found a good reason to keep them. :-)
> > 
> > What about .sh suffix? Should be most portable way.
> 
> That's the approach I tend to follow for my sh code.  Explicit is
> better than implicit if you ask me.

I would certainly agree for new files.

> Kevin,
> 
> Do you have any strong feelings here?  I'd be fine with either this
> or dropping the patch.

No strong feelings. The result of renaming the files would be a bit
nicer than what we have today, but renaming always comes with a cost
when working with the version history later. Hard to tell if it's a net
gain or loss in the end.

Myself, I would probably pick the lazy way and stick with "if it ain't
broke, don't fix it", but I'm not objecting to a change either.

Kevin


  reply	other threads:[~2019-10-11 20:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 19:47 [PATCH v2 0/4] iotests: trivial cleanups Cleber Rosa
2019-10-09 19:47 ` Cleber Rosa
2019-10-09 19:47 ` [PATCH v2 1/4] qemu-iotests: remove bash shebang from library files Cleber Rosa
2019-10-09 19:47   ` Cleber Rosa
2019-10-09 19:51   ` Eric Blake
2019-10-09 19:51     ` Eric Blake
2019-10-09 20:54     ` Cleber Rosa
2019-10-09 20:54       ` Cleber Rosa
2019-10-11  9:36   ` Kevin Wolf
2019-10-11  9:36     ` Kevin Wolf
2019-10-11 11:27     ` Nir Soffer
2019-10-11 11:27       ` Nir Soffer
2019-10-11 20:05       ` Cleber Rosa
2019-10-11 20:30         ` Kevin Wolf [this message]
2019-10-11 20:30           ` Kevin Wolf
2019-10-09 19:47 ` [PATCH v2 2/4] qemu-iotests: remove forceful execution success " Cleber Rosa
2019-10-09 19:47   ` Cleber Rosa
2019-10-11 11:25   ` Kevin Wolf
2019-10-11 11:25     ` Kevin Wolf
2019-10-09 19:47 ` [PATCH v2 3/4] qemu-iotests: 044: pass is actually a noop, so remove it Cleber Rosa
2019-10-09 19:47   ` Cleber Rosa
2019-10-10 11:27   ` Philippe Mathieu-Daudé
2019-10-11 11:26   ` Kevin Wolf
2019-10-11 11:26     ` Kevin Wolf
2019-10-09 19:47 ` [PATCH v2 4/4] qemu-iotests: 044: remove inaccurate docstring class description Cleber Rosa
2019-10-09 19:47   ` Cleber Rosa
2019-10-11 11:27   ` Kevin Wolf
2019-10-11 11:27     ` Kevin Wolf

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=20191011203046.GI5158@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=crosa@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=mjt@tls.msk.ru \
    --cc=mreitz@redhat.com \
    --cc=nsoffer@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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.