git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Miriam Rubio <mirucam@gmail.com>
To: git@vger.kernel.org
Cc: rafaeloliveira.cs@gmail.com, Miriam Rubio <mirucam@gmail.com>
Subject: [PATCH v5 0/7] Finish converting git bisect to C part 3
Date: Wed,  3 Feb 2021 22:54:31 +0100	[thread overview]
Message-ID: <20210203215438.96760-1-mirucam@gmail.com> (raw)

These patches correspond to a third 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 third part is formed by reimplementations of some `git bisect` 
subcommands and removal of some temporary subcommands.

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

I would like to thank Christian Couder and Đoàn Trần Công Danh for their
reviews and suggestions.

Specific changes
----------------

[1/7] bisect--helper: reimplement `bisect_log` shell function in C
* Add return error message.
* Add helped-by trailer in commit message. 
---

[2/7] bisect--helper: reimplement `bisect_replay` shell function in C
* Remove braces.
----

[3/7] bisect--helper: retire `--bisect-write` subcommand
* Remove break statement.
----

[4/7] bisect--helper: use `res` instead of return in BISECT_RESET case
* Add break statement.
----

Pranit Bauva (7):
  bisect--helper: reimplement `bisect_log` shell function in C
  bisect--helper: reimplement `bisect_replay` shell function in C
  bisect--helper: retire `--bisect-write` subcommand
  bisect--helper: use `res` instead of return in BISECT_RESET case
    option
  bisect--helper: retire `--bisect-auto-next` subcommand
  bisect--helper: reimplement `bisect_skip` shell function in C
  bisect--helper: retire `--check-and-set-terms` subcommand

 builtin/bisect--helper.c | 183 ++++++++++++++++++++++++++++++++-------
 git-bisect.sh            |  58 +------------
 2 files changed, 155 insertions(+), 86 deletions(-)

-- 
2.29.2


             reply	other threads:[~2021-02-03 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 21:54 Miriam Rubio [this message]
2021-02-03 21:54 ` [PATCH v5 1/7] bisect--helper: reimplement `bisect_log` shell function in C Miriam Rubio
2021-02-03 21:54 ` [PATCH v5 2/7] bisect--helper: reimplement `bisect_replay` " Miriam Rubio
2021-02-03 21:54 ` [PATCH v5 3/7] bisect--helper: retire `--bisect-write` subcommand Miriam Rubio
2021-02-03 21:54 ` [PATCH v5 4/7] bisect--helper: use `res` instead of return in BISECT_RESET case option Miriam Rubio
2021-02-03 21:54 ` [PATCH v5 5/7] bisect--helper: retire `--bisect-auto-next` subcommand Miriam Rubio
2021-02-03 21:54 ` [PATCH v5 6/7] bisect--helper: reimplement `bisect_skip` shell function in C Miriam Rubio
2021-02-03 21:54 ` [PATCH v5 7/7] bisect--helper: retire `--check-and-set-terms` subcommand Miriam Rubio

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210203215438.96760-1-mirucam@gmail.com \
    --to=mirucam@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=rafaeloliveira.cs@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).