From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/3] merge: allow reading the merge commit message from a file
Date: Thu, 12 Jul 2018 14:58:59 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1807121455130.75@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqbmbd1l7i.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, 11 Jul 2018, Junio C Hamano wrote:
> "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
> writes:
>
> > diff --git a/builtin/merge.c b/builtin/merge.c
> > index 4a4c09496..b0e907751 100644
> > --- a/builtin/merge.c
> > +++ b/builtin/merge.c
> > @@ -111,6 +111,35 @@ static int option_parse_message(const struct option *opt,
> > return 0;
> > }
> >
> > +static int option_read_message(struct parse_opt_ctx_t *ctx,
> > + const struct option *opt, int unset)
> > +{
> > + struct strbuf *buf = opt->value;
> > + const char *arg;
> > +
> > + if (unset)
> > + BUG("-F cannot be negated");
>
> The message "-F cannot be negated" looks as if it is pointing out a
> mistake by the end user, and does not mesh well with the real reason
> why this is BUG() and is not die().
>
> I understand that this is BUG() not die() because options[] array
> tells this callback not to be called with unset by having the
> PARSE_OPT_NONEG bit there.
Okay. I would have appreciated some sort of indication what you prefer
instead. I went with "--no-file?!?"
> > + if (ctx->opt) {
> > + arg = ctx->opt;
> > + ctx->opt = NULL;
> > + } else if (ctx->argc > 1) {
> > + ctx->argc--;
> > + arg = *++ctx->argv;
> > + } else
> > + return opterror(opt, "requires a value", 0);
> > +
> > + if (buf->len)
> > + strbuf_addch(buf, '\n');
>
> Do we assume that buf, if it is not empty, is properly terminated
> with LF already? I am wondering if the real reason we do these two
> lines is to make sure we have a separating blank line between what
> is already there (if there already is something) and what we add, in
> which case the above would want to say
>
> if (buf->len) {
> strbuf_complete_line(buf);
> strbuf_addch(buf, '\n');
> }
>
> instead.
True. Thanks for the suggestion!
> > + if (ctx->prefix && !is_absolute_path(arg))
> > + arg = prefix_filename(ctx->prefix, arg);
> > + if (strbuf_read_file(buf, arg, 0) < 0)
> > + return error(_("could not read file '%s'"), arg);
> > + have_message = 1;
>
> A similar question is what we would want to do when the file ends
> with an incomplete line. With "--log", we would be appending more
> stuff to buf, and we'd want to complete such an incomplete line
> before that happens, either here or in the code immediately before
> "--log" is processed.
This is what I inserted here:
strbuf_complete_line(buf);
> > +
> > + return 0;
> > +}
> > +
> > static struct strategy *get_strategy(const char *name)
> > {
> > int i;
Thanks for the review, and especially for the suggestions how to improve
the code.
Ciao,
Dscho
next prev parent reply other threads:[~2018-07-12 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 12:38 [PATCH 0/3] rebase -r: support octopus merges Johannes Schindelin via GitGitGadget
2017-12-21 14:52 ` [PATCH 2/3] rebase --rebase-merges: add support for " Johannes Schindelin via GitGitGadget
2018-07-11 18:49 ` Eric Sunshine
2018-07-11 21:52 ` Junio C Hamano
2018-07-12 13:11 ` Johannes Schindelin
2018-07-12 13:08 ` Johannes Schindelin
2017-12-22 14:10 ` [PATCH 1/3] merge: allow reading the merge commit message from a file Johannes Schindelin via GitGitGadget
2018-07-11 22:06 ` Junio C Hamano
2018-07-12 12:58 ` Johannes Schindelin [this message]
2018-07-12 16:20 ` Junio C Hamano
2018-03-09 16:36 ` [PATCH 3/3] rebase --rebase-merges: adjust man page for octopus support Johannes Schindelin via GitGitGadget
2018-07-11 17:05 ` Elijah Newren
2018-07-12 12:48 ` Johannes Schindelin
2018-07-11 17:35 ` [PATCH 0/3] rebase -r: support octopus merges Junio C Hamano
2018-07-11 17:47 ` Stefan Beller
2018-07-12 12:54 ` Johannes Schindelin
2018-07-12 16:26 ` Junio C Hamano
2018-07-13 16:42 ` Johannes Sixt
2018-07-16 17:56 ` Junio C Hamano
2018-07-12 12:49 ` 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
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=nycvar.QRO.7.76.6.1807121455130.75@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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).