git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] t9803: update commit messages and description

From
SJSanchit Jindal <sanchit1053@gmail.com>
Date
Mar 21, 2024, 20:28 UTC
Message-ID
<CAN7Jk_3A5c=5E+CNyncaT9qe_d85_p6ZHNzJPd0E5ZSjG1kQng@mail.gmail.com>
In-Reply-To
<CAPig+cRweMree1LJ=qpOJZg7HYvgE9XX8iFvMKcAGYJpAFGFDg@mail.gmail.com>
On Fri, 22 Mar 2024 at 01:22, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 34 quoted lines
>
> On Thu, Mar 21, 2024 at 3:39 PM Sanchit Jindal via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
> > From: Sanchit Jindal <sanchit1053@gmail.com>
> >
> > replacing `test -e` with test_path_exists,
> >           `test ! -e` with test_path_is_missing
> >           `test -f` with test_path_is_file
> > These helper functions will run the `test` command with the
> > corresponding flags and will echo a message if the assert fails.
> > This will provide better debugging logs for test, instead of the
> > previous method which provided no message
> >
> > Signed-off-by: Sanchit Jindal <sanchit1053@gmail.com>
>
> When rerolling a series to address reviewer comments, you will want
> the fixes applied directly to the patches about which the reviewers
> commented. The way to do this is to use `git rebase -i` to adjust the
> patches as needed. In the case of this simple series, you just want to
> "squash" patches [1/2] and [2/2] into a single patch using the `git
> rebase -i` "squash" command, and adjust the commit message of the
> squashed patch appropriately. Finally, to resubmit it via
> GitGitGadget, force-push the revised series to GitGitGadget (using
> `git push --force <whatever> <whatever>`), and tell GitGitGadget to
> "/submit".
>
> Regarding the commit message, first explain the problem the patch is
> solving, and then explain how the patch solves it. Thus, start by
> explaining that `test` doesn't provide any diagnostic information when
> it fails, which isn't helpful to test authors. Then explain that the
> patch replaces `test` with the test_path_* functions which do provide
> useful diagnostic information.
>
> The From: and Signed-off-by: lines look good in this reroll.
Thank You for the review

I renamed the branch using github as it had a typo which made the earlier patch to be erased.I am extremely sorry about this.

I have created another patch with a more descriptive commit message, and after squashing it with the earlier commit. I hope it is satisfactory

I wanted to ask, Is it possible to send the patches created using `git format-patch` manually using gmail, Or the default headers applied by `send-email` required.

Regards, Sanchit Jindal

Previous: Eric SunshineNext: Junio C Hamano
Message 5 of 9 in “t9803-git-p4-shell-metachars.sh: update to use test_path_* functions”
  1. 0/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionsSanchit Jindal via GitGitGadget, Mar 21, 2024
  2. 1/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionssanchit1053 via GitGitGadget, Mar 21, 2024
  3. 2/2 t9803: update commit messages and descriptionSanchit Jindal via GitGitGadget, Mar 21, 2024
  4. Eric SunshineMar 21, 2024
  5. Sanchit JindalMar 21, 2024
  6. Junio C HamanoMar 21, 2024
  7. 0/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionsSanchit Jindal via GitGitGadget, Mar 21, 2024
  8. 1/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionssanchit1053 via GitGitGadget, Mar 21, 2024
  9. 2/2 t9803: update commit messages and descriptionSanchit Jindal via GitGitGadget, Mar 21, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.