From: Sergey Organov <sorganov@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Thomas Rast" <tr@thomasrast.ch>,
"Denton Liu" <liu.denton@gmail.com>,
"Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: [PATCH v3] stash: implement '--staged' option for 'push' and 'save'
Date: Wed, 27 Oct 2021 18:11:19 +0300 [thread overview]
Message-ID: <8735ombizs.fsf@osv.gnss.ru> (raw)
In-Reply-To: <YXeMkC/jPxjzNgWF@coredump.intra.peff.net> (Jeff King's message of "Tue, 26 Oct 2021 01:05:20 -0400")
Jeff King <peff@peff.net> writes:
> On Mon, Oct 18, 2021 at 07:09:06PM +0300, Sergey Organov wrote:
>
>> +static int stash_staged(struct stash_info *info, const struct pathspec *ps,
>> + struct strbuf *out_patch, int quiet)
>> +{
>> + int ret = 0;
>> + struct child_process cp_diff_tree = CHILD_PROCESS_INIT;
>> + struct index_state istate = { NULL };
>> +
>> + if (write_index_as_tree(&info->w_tree, &istate,
>> the_repository->index_file,
>> + 0, NULL)) {
>> + ret = -1;
>> + goto done;
>> + }
>> +
>> + cp_diff_tree.git_cmd = 1;
>> + strvec_pushl(&cp_diff_tree.args, "diff-tree", "-p", "-U1", "HEAD",
>> + oid_to_hex(&info->w_tree), "--", NULL);
>> + if (pipe_command(&cp_diff_tree, NULL, 0, out_patch, 0, NULL, 0)) {
>> + ret = -1;
>> + goto done;
>> + }
>> +
>> + if (!out_patch->len) {
>> + if (!quiet)
>> + fprintf_ln(stderr, _("No staged changes"));
>> + ret = 1;
>> + }
>> +
>> +done:
>> + discard_index(&istate);
>> + return ret;
>> +}
>
> This function doesn't look at its "struct pathspec" parameter at all.
> I'm not sure if that's a bug (i.e., it should be restricting the diff
> here) or if it was just pulled unnecessarily over from stash_patch().
Yep, it's a remnant from copy-paste of stash_patch(). I'm used to
getting a warning from compiler for such cases and didn't pay enough
attention. The warning belongs to -Wextra though and is not turned on
for Git compilation.
Thanks for catching!
-- Sergey Organov
next prev parent reply other threads:[~2021-10-27 15:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 22:12 [PATCH RFC] stash: implement '--staged' option for 'push' and 'save' Sergey Organov
2021-10-11 20:16 ` [PATCH RFC v1] " Sergey Organov
2021-10-11 21:21 ` Eric Sunshine
2021-10-11 21:55 ` Sergey Organov
2021-10-12 9:18 ` Ævar Arnfjörð Bjarmason
2021-10-12 11:20 ` Sergey Organov
2021-10-12 12:04 ` Junio C Hamano
2021-10-12 12:34 ` Junio C Hamano
2021-10-12 16:07 ` Sergey Organov
2021-10-12 17:28 ` Junio C Hamano
2021-10-12 18:25 ` Sergey Organov
2021-10-13 4:48 ` Junio C Hamano
2021-10-13 13:43 ` Sergey Organov
2021-10-15 15:04 ` [PATCH v2] " Sergey Organov
2021-10-15 17:58 ` Junio C Hamano
2021-10-15 19:05 ` Sergey Organov
2021-10-15 19:22 ` Junio C Hamano
2021-10-15 20:14 ` Sergey Organov
2021-10-15 20:21 ` Sergey Organov
2021-10-18 16:09 ` [PATCH v3] " Sergey Organov
2021-10-26 5:05 ` Jeff King
2021-10-27 15:11 ` Sergey Organov [this message]
2021-10-27 15:20 ` [PATCH v4] " Sergey Organov
2021-10-27 21:19 ` Junio C Hamano
2021-10-28 8:29 ` [PATCH] stash: get rid of unused argument in stash_staged() Sergey Organov
2021-10-28 21:17 ` Junio C Hamano
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=8735ombizs.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=liu.denton@gmail.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
--cc=tr@thomasrast.ch \
/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).