From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] esed.eclass: new eclass
Date: Tue, 31 May 2022 09:45:14 -0400 [thread overview]
Message-ID: <YpYb6qKoSEzN4Uva@eversor> (raw)
In-Reply-To: <20220531112319.29168-2-ionen@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Tue, May 31, 2022 at 07:23:18AM -0400, Ionen Wolkens wrote:
> + if [[ ${contents[i]} != "${newcontents}" ]]; then
> + changed=1
> + [[ -v verbose ]] || break
> + fi
> +
> + [[ -v verbose ]] &&
> + diff -u --color --label="${files[i]}"{,} \
> + <(echo "${contents[i]}") <(echo "${newcontents}")
self nitpick, didn't think much of these given optional but diff has
nothing to say if contents == newcontents so will replace with:
if [[ ${contents[i]} != "${newcontents}" ]]; then
changed=1
[[ -v verbose ]] || break
diff -u --color --label="${files[i]}"{,} \
<(echo "${contents[i]}") <(echo "${newcontents}")
fi
> + [[ ${contents} != "${newcontents}" ]] && changed=1
> +
> + [[ -v verbose ]] &&
> + diff -u --color --label="${files[*]}" --label="${_esed_output}" \
> + <(echo "${contents}") <(echo "${newcontents}")
and:
if [[ ${contents} != "${newcontents}" ]]; then
changed=1
[[ -v verbose ]] &&
diff -u --color --label="${files[*]}" --label="${_esed_output}" \
<(echo "${contents}") <(echo "${newcontents}")
fi
(updated on github PR)
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-31 13:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 11:23 [gentoo-dev] [PATCH 0/2] Add esed.eclass for sed that dies if caused no changes Ionen Wolkens
2022-05-31 11:23 ` [gentoo-dev] [PATCH 1/2] esed.eclass: new eclass Ionen Wolkens
2022-05-31 13:45 ` Ionen Wolkens [this message]
2022-06-03 7:14 ` Ulrich Mueller
2022-06-03 9:26 ` Ionen Wolkens
2022-06-03 11:19 ` Ionen Wolkens
2022-05-31 11:23 ` [gentoo-dev] [PATCH 2/2] eclass/tests/esed.sh: basic tests for esed.eclass Ionen Wolkens
2022-05-31 13:54 ` [gentoo-dev] [PATCH 0/2] Add esed.eclass for sed that dies if caused no changes Anna
2022-05-31 14:29 ` Ionen Wolkens
2022-05-31 14:44 ` Jaco Kroon
2022-06-03 4:09 ` Michał Górny
2022-06-03 4:45 ` Ionen Wolkens
2022-06-03 4:47 ` Anna V
2022-06-03 5:01 ` Ionen Wolkens
2022-06-03 5:00 ` Anna V
2022-06-03 5:05 ` Ionen Wolkens
2022-06-03 4:59 ` Sam James
2022-06-03 5:02 ` Sam James
2022-06-03 11:36 ` [gentoo-dev] [PATCH v2 0/1] esed Ionen Wolkens
2022-06-03 11:36 ` [gentoo-dev] [PATCH v2 1/1] esed.eclass: new eclass Ionen Wolkens
2022-06-04 0:15 ` Oskari Pirhonen
2022-06-04 7:00 ` Ionen Wolkens
2022-06-03 14:13 ` [gentoo-dev] [PATCH v2 0/1] esed Ionen Wolkens
2022-06-04 16:19 ` [gentoo-dev] [PATCH 0/2] Add esed.eclass for sed that dies if caused no changes Alessandro Barbieri
2022-06-04 16:53 ` Ionen Wolkens
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=YpYb6qKoSEzN4Uva@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox