Remi Galan Alfonso remi.galan-alfo...@ensimag.grenoble-inp.fr writes:
Matthieu Moy matthieu@grenoble-inp.fr writes:
Remi Galan Alfonso remi.galan-alfo...@ensimag.grenoble-inp.fr writes:
It is mainly because here the SHA-1 is a long one (40 chars)
OK, but then the minimum would be to
Matthieu Moy matthieu@grenoble-inp.fr writes:
Remi Galan Alfonso remi.galan-alfo...@ensimag.grenoble-inp.fr writes:
It is mainly because here the SHA-1 is a long one (40 chars)
OK, but then the minimum would be to add a comment saying that.
Now, this makes me wonder why you are
Check before the start of the rebasing if the commands exists, and for
the commands expecting a SHA-1, check if the SHA-1 is present and
corresponds to a commit. In case of error, print the error, stop git
rebase and prompt the user to fix with 'git rebase --edit-todo' or to
abort.
This allows to
Remi Galan Alfonso remi.galan-alfo...@ensimag.grenoble-inp.fr writes:
It is mainly because here the SHA-1 is a long one (40 chars)
OK, but then the minimum would be to add a comment saying that.
Now, this makes me wonder why you are doing the check after the sha1
expansion and not before.
+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)
+
Galan Rémi remi.galan-alfo...@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)
+
6 matches
Mail list logo
