From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: "Galan Rémi" <remi.galan-alfonso@ensimag.grenoble-inp.fr>
Cc: Git List <git@vger.kernel.org>,
Remi Lespinet <remi.lespinet@ensimag.grenoble-inp.fr>,
Guillaume Pages <guillaume.pages@ensimag.grenoble-inp.fr>,
Louis-Alexandre Stuber
<louis--alexandre.stuber@ensimag.grenoble-inp.fr>,
Antoine Delaite <antoine.delaite@ensimag.grenoble-inp.fr>,
Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH/RFCv5 3/3] git rebase -i: add static check for commands and SHA-1
Date: Wed, 10 Jun 2015 17:20:47 +0200 [thread overview]
Message-ID: <vpq8ubrtws0.fsf@anie.imag.fr> (raw)
In-Reply-To: <1433931035-20011-3-git-send-email-remi.galan-alfonso@ensimag.grenoble-inp.fr> ("Galan \=\?iso-8859-1\?Q\?R\=E9mi\=22's\?\= message of "Wed, 10 Jun 2015 12:10:35 +0200")
Galan Rémi <remi.galan-alfonso@ensimag.grenoble-inp.fr> writes:
> +# from the todolist in stdin
> +check_bad_cmd_and_sha () {
> + git stripspace --strip-comments |
> + while read -r command sha1 rest
> + do
> + case $command in
> + ''|noop|x|"exec")
> + ;;
> + pick|p|drop|d|reword|r|edit|e|squash|s|fixup|f)
> + if test -z $sha1
> + then
> + echo "$command $rest" >>"$todo".badsha
> + else
> + sha1_verif="$(git rev-parse --verify --quiet $sha1^{commit})"
> + if test -z $sha1_verif
> + then
> + echo "$command $sha1 $rest" \
> + >>"$todo".badsha
When you reach the right end of your screen because of indentation,
cutting lines with \ is rarely the best option. Having 5 levels of
indentation is a sign that you should make more functions.
How about:
check_bad_cmd_and_sha () {
git stripspace --strip-comments |
while read -r command sha1 rest
do
case $command in
''|noop|x|"exec")
;;
pick|p|drop|d|reword|r|edit|e|squash|s|fixup|f)
check_commit_id $sha1
;;
*)
record_bad_command $sha1
;;
esac
}
?
> + *)
> + if test -z $sha1
> + then
> + echo "$command" >>"$todo".badcmd
Avoid echo on user-supplied data.
> + else
> + commit="$(git rev-list --oneline -1 --ignore-missing $sha1 2>/dev/null)"
> + if test -z "$commit"
> + then
> + echo "$command $sha1 $rest" \
> + >>"$todo".badcmd
> + else
> + echo "$command $commit" >>"$todo".badcmd
> + fi
> + fi
What are you trying to do here? It seems that you are trying to recover
the line, but the line is your input, you shouldn't have to recompute
it.
Why isn't printf '%s %s %s' "$command" "$sha1" "$rest" sufficient in all
cases?
Maybe it would be better to read line by line (to avoid loosing
whitespace information for example), like
while read -r line
do
printf '%s' "$line" | read -r cmd sha1 rest
case $sha1 in
...
or maybe it's overkill.
> + check_bad_cmd_and_sha <"$todo"
> +
> + if test -s "$todo".badsha
> + then
> + raiseError=t
We usually don't use camelCase in shell-scripts. raise_error would be
the usual way to spell in in Git's codebase.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-06-10 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 10:10 [PATCH/RFCv5 1/3] git-rebase -i: add command "drop" to remove a commit Galan Rémi
2015-06-10 10:10 ` [PATCH/RFCv5 2/3] git rebase -i: warn about removed commits Galan Rémi
2015-06-10 14:53 ` Matthieu Moy
2015-06-10 15:47 ` Remi Galan Alfonso
2015-06-10 15:55 ` Matthieu Moy
2015-06-10 15:59 ` Remi Galan Alfonso
2015-06-10 10:10 ` [PATCH/RFCv5 3/3] git rebase -i: add static check for commands and SHA-1 Galan Rémi
2015-06-10 15:20 ` Matthieu Moy [this message]
2015-06-10 15:56 ` Remi Galan Alfonso
2015-06-10 16:08 ` Matthieu Moy
2015-06-13 23:17 ` Remi Galan Alfonso
2015-06-15 8:25 ` Matthieu Moy
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=vpq8ubrtws0.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=antoine.delaite@ensimag.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=guillaume.pages@ensimag.grenoble-inp.fr \
--cc=louis--alexandre.stuber@ensimag.grenoble-inp.fr \
--cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
--cc=remi.lespinet@ensimag.grenoble-inp.fr \
--cc=sunshine@sunshineco.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 NNTP newsgroup(s).