git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miriam Rubio <mirucam@gmail.com>
To: git@vger.kernel.org
Cc: Miriam Rubio <mirucam@gmail.com>
Subject: [PATCH v5 0/6] Finish converting git bisect to C part 4
Date: Fri, 20 Aug 2021 19:21:42 +0200	[thread overview]
Message-ID: <20210820172148.2249-1-mirucam@gmail.com> (raw)

These patches correspond to a fourth part of patch series 
of Outreachy project "Finish converting `git bisect` from shell to C" 
started by Pranit Bauva and Tanushree Tumane
(https://public-inbox.org/git/pull.117.git.gitgitgadget@gmail.com) and
continued by me.

This fourth part is formed by reimplementations of some `git bisect` 
subcommands, addition of tests and removal of some temporary subcommands.

These patch series emails were generated from:
https://gitlab.com/mirucam/git/commits/git-bisect-work-part4-v5.

I would like to thank Johannes Schindelin, Bagas Sanjaya and 
Christian Couder for reviewing this patch series.

Specific changes
----------------
[1/6] t6030-bisect-porcelain: add tests to control bisect run exit cases
* Add evaluation of error code 255 in test 'bisect run fails with exit 
code equals or greater than 128'.
* Remove test with error code smaller than 0.
---

[4/6] bisect--helper: reimplement `bisect_visualize()`shell function in C
* Use strvec_push() instead of strvec_pushl().
---

[5/6] bisect--helper: reimplement `bisect_run` shell function in C
* Add error message.
* Remove exit variable.
* Write contents of bisect_state() in BISECT_RUN file and show to user.
---

Miriam Rubio (3):
  t6030-bisect-porcelain: add tests to control bisect run exit cases
  t6030-bisect-porcelain: add test for bisect visualize
  bisect--helper: retire `--bisect-next-check` subcommand

Pranit Bauva (2):
  run-command: make `exists_in_PATH()` non-static
  bisect--helper: reimplement `bisect_visualize()`shell function in C

Tanushree Tumane (1):
  bisect--helper: reimplement `bisect_run` shell function in C

 builtin/bisect--helper.c    | 157 ++++++++++++++++++++++++++++++++++--
 git-bisect.sh               |  87 +-------------------
 run-command.c               |   2 +-
 run-command.h               |  12 +++
 t/t6030-bisect-porcelain.sh |  18 +++++
 5 files changed, 182 insertions(+), 94 deletions(-)

-- 
2.29.2


             reply	other threads:[~2021-08-20 17:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 17:21 Miriam Rubio [this message]
2021-08-20 17:21 ` [PATCH v5 1/6] t6030-bisect-porcelain: add tests to control bisect run exit cases Miriam Rubio
2021-08-20 17:21 ` [PATCH v5 2/6] t6030-bisect-porcelain: add test for bisect visualize Miriam Rubio
2021-08-20 17:21 ` [PATCH v5 3/6] run-command: make `exists_in_PATH()` non-static Miriam Rubio
2021-08-20 17:21 ` [PATCH v5 4/6] bisect--helper: reimplement `bisect_visualize()`shell function in C Miriam Rubio
2021-08-20 17:21 ` [PATCH v5 5/6] bisect--helper: reimplement `bisect_run` shell " Miriam Rubio
2021-08-24 13:59   ` Johannes Schindelin
2021-08-26 16:46     ` Miriam R.
2021-08-20 17:21 ` [PATCH v5 6/6] bisect--helper: retire `--bisect-next-check` subcommand Miriam Rubio
2021-08-24 14:00 ` [PATCH v5 0/6] Finish converting git bisect to C part 4 Johannes Schindelin

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=20210820172148.2249-1-mirucam@gmail.com \
    --to=mirucam@gmail.com \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).