From: Eric Sunshine <sunshine@sunshineco.com> To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com> Cc: "Git List" <git@vger.kernel.org>, "Junio C Hamano" <gitster@pobox.com>, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, tim@tim-landscheidt.de Subject: Re: [PATCH v2 1/3] am: add --show-current-patch Date: Wed, 31 Jan 2018 04:40:46 -0500 [thread overview] Message-ID: <CAPig+cR24=0_NPekYaF+oG9OovDkv1Et-RpNvAHqE7Qd7g7QQA@mail.gmail.com> (raw) In-Reply-To: <20180131093051.15525-2-pclouds@gmail.com> On Wed, Jan 31, 2018 at 4:30 AM, Nguyễn Thái Ngọc Duy <pclouds@gmail.com> wrote: > Pointing the user to $GIT_DIR/rebase-apply may encourage them to mess > around in there, which is not a good thing. With this, the user does > not have to keep the path around somewhere (because after a couple of > commands, the path may be out of scrollback buffer) when they need to > look at the patch. > > Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> > --- > diff --git a/builtin/am.c b/builtin/am.c > @@ -2121,6 +2120,22 @@ static void am_abort(struct am_state *state) > +static int show_patch(struct am_state *state) > +{ > + struct strbuf sb = STRBUF_INIT; > + int len; > + > + len = strbuf_read_file(&sb, am_path(state, msgnum(state)), 0); > + if (len < 0) > + die_errno(_("failed to read '%s'"), > + am_path(state, msgnum(state))); Isn't this am_path() invocation inside die_errno() likely to clobber the 'errno' from strbuf_read_file() which you want to be reporting? > + setup_pager(); > + write_in_full(1, sb.buf, sb.len); > + strbuf_release(&sb); > + return 0; > +}
next prev parent reply other threads:[~2018-01-31 9:40 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-26 9:55 [PATCH 0/2] Add "git rebase --show-patch" Nguyễn Thái Ngọc Duy 2018-01-26 9:55 ` [PATCH 1/2] am: add --show-patch Nguyễn Thái Ngọc Duy 2018-01-26 9:55 ` [PATCH 2/2] rebase: " Nguyễn Thái Ngọc Duy 2018-01-26 11:12 ` Phillip Wood 2018-01-26 11:22 ` Duy Nguyen 2018-01-30 11:15 ` Phillip Wood 2018-01-26 19:11 ` Eric Sunshine 2018-01-27 1:42 ` Duy Nguyen 2018-01-26 18:47 ` [PATCH 0/2] Add "git rebase --show-patch" Tim Landscheidt 2018-01-27 1:45 ` Duy Nguyen 2018-01-27 11:26 ` Ævar Arnfjörð Bjarmason 2018-01-29 15:09 ` Johannes Schindelin 2018-01-30 9:10 ` Duy Nguyen 2018-01-30 12:32 ` Johannes Schindelin 2018-01-30 20:19 ` Junio C Hamano 2018-02-01 2:06 ` Tim Landscheidt 2018-01-31 9:30 ` [PATCH v2 0/3] " Nguyễn Thái Ngọc Duy 2018-01-31 9:30 ` [PATCH v2 1/3] am: add --show-current-patch Nguyễn Thái Ngọc Duy 2018-01-31 9:40 ` Eric Sunshine [this message] 2018-01-31 22:59 ` Junio C Hamano 2018-02-02 9:25 ` Duy Nguyen 2018-02-02 9:46 ` Eric Sunshine 2018-02-02 9:53 ` Duy Nguyen 2018-02-02 18:56 ` Junio C Hamano 2018-01-31 9:30 ` [PATCH] gitignore.txt: elaborate shell glob syntax Nguyễn Thái Ngọc Duy 2018-01-31 23:22 ` Junio C Hamano 2018-02-01 9:59 ` Duy Nguyen 2018-01-31 9:30 ` [PATCH v2 2/3] rebase: add --show-current-patch Nguyễn Thái Ngọc Duy 2018-01-31 9:30 ` [PATCH v2 3/3] rebase: introduce and use pseudo-ref ORIG_COMMIT Nguyễn Thái Ngọc Duy 2018-01-31 23:18 ` Junio C Hamano 2018-02-01 10:02 ` Duy Nguyen 2018-02-02 19:00 ` Junio C Hamano 2018-02-01 11:05 ` Phillip Wood 2018-02-11 9:43 ` [PATCH v3 0/3] Add "git rebase --show-current-patch" Nguyễn Thái Ngọc Duy 2018-02-11 9:43 ` [PATCH v3 1/3] am: add --show-current-patch Nguyễn Thái Ngọc Duy 2018-02-11 9:43 ` [PATCH v3 2/3] rebase: " Nguyễn Thái Ngọc Duy 2018-02-11 9:43 ` [PATCH v3 3/3] rebase: introduce and use pseudo-ref REBASE_HEAD Nguyễn Thái Ngọc Duy 2018-02-22 0:21 ` [PATCH v3 0/3] Add "git rebase --show-current-patch" Junio C Hamano 2018-02-22 0:54 ` Tim Landscheidt 2018-02-23 10:20 ` Duy Nguyen
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='CAPig+cR24=0_NPekYaF+oG9OovDkv1Et-RpNvAHqE7Qd7g7QQA@mail.gmail.com' \ --to=sunshine@sunshineco.com \ --cc=Johannes.Schindelin@gmx.de \ --cc=avarab@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=pclouds@gmail.com \ --cc=tim@tim-landscheidt.de \ --subject='Re: [PATCH v2 1/3] am: add --show-current-patch' \ /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
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).