All of lore.kernel.org
 help / color / mirror / Atom feed
From: 林自均 <johnlinp@gmail.com>
To: Phil Hord <phil.hord@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: [PATCH] status: add an empty line when there is no hint
Date: Tue, 30 Apr 2019 12:46:44 +0800	[thread overview]
Message-ID: <CAKO26MswBM5sjuVSnxssOc4jd+hqXiko=+6ROatOm2H7jndujA@mail.gmail.com> (raw)
In-Reply-To: <CABURp0rSTT=8biNhBvsGP4fdEHBT4B5beVKsm=Mdp7Ei8Dw72w@mail.gmail.com>

Hi Phil,

Thank you for the review! I will fix the test cases and submit a new
version of my patch.

Best,
John Lin

Phil Hord <phil.hord@gmail.com> 於 2019年4月30日 週二 上午11:12寫道:
>
> You should probably add some test that demonstrates what your change
> intends to do.  For that matter, though, your test already breaks at
> least two tests in t7508-status.sh:
>
> not ok 14 - status (advice.statusHints false)
> not ok 23 - status -uno (advice.statusHints false)
>
> Phil
>
> On Tue, Apr 23, 2019 at 2:21 AM John Lin <johnlinp@gmail.com> wrote:
> >
> > When typing "git status", there is an empty line between
> > the "Changes not staged for commit:" block and the list
> > of changed files. However, when typing "git commit" with
> > no files added, there are no empty lines between them.
> >
> > This patch adds empty lines in the above case and some
> > similar cases.
> >
> > Signed-off-by: John Lin <johnlinp@gmail.com>
> > ---
> >  wt-status.c | 12 ++++++++----
> >  1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/wt-status.c b/wt-status.c
> > index 445a36204a..0766e3ee12 100644
> > --- a/wt-status.c
> > +++ b/wt-status.c
> > @@ -175,7 +175,7 @@ static void wt_longstatus_print_unmerged_header(struct wt_status *s)
> >         }
> >
> >         if (!s->hints)
> > -               return;
> > +               goto conclude;
> >         if (s->whence != FROM_COMMIT)
> >                 ;
> >         else if (!s->is_initial)
> > @@ -193,6 +193,7 @@ static void wt_longstatus_print_unmerged_header(struct wt_status *s)
> >         } else {
> >                 status_printf_ln(s, c, _("  (use \"git add/rm <file>...\" as appropriate to mark resolution)"));
> >         }
> > +conclude:
> >         status_printf_ln(s, c, "%s", "");
> >  }
> >
> > @@ -202,13 +203,14 @@ static void wt_longstatus_print_cached_header(struct wt_status *s)
> >
> >         status_printf_ln(s, c, _("Changes to be committed:"));
> >         if (!s->hints)
> > -               return;
> > +               goto conclude;
> >         if (s->whence != FROM_COMMIT)
> >                 ; /* NEEDSWORK: use "git reset --unresolve"??? */
> >         else if (!s->is_initial)
> >                 status_printf_ln(s, c, _("  (use \"git reset %s <file>...\" to unstage)"), s->reference);
> >         else
> >                 status_printf_ln(s, c, _("  (use \"git rm --cached <file>...\" to unstage)"));
> > +conclude:
> >         status_printf_ln(s, c, "%s", "");
> >  }
> >
> > @@ -220,7 +222,7 @@ static void wt_longstatus_print_dirty_header(struct wt_status *s,
> >
> >         status_printf_ln(s, c, _("Changes not staged for commit:"));
> >         if (!s->hints)
> > -               return;
> > +               goto conclude;
> >         if (!has_deleted)
> >                 status_printf_ln(s, c, _("  (use \"git add <file>...\" to update what will be committed)"));
> >         else
> > @@ -228,6 +230,7 @@ static void wt_longstatus_print_dirty_header(struct wt_status *s,
> >         status_printf_ln(s, c, _("  (use \"git checkout -- <file>...\" to discard changes in working directory)"));
> >         if (has_dirty_submodules)
> >                 status_printf_ln(s, c, _("  (commit or discard the untracked or modified content in submodules)"));
> > +conclude:
> >         status_printf_ln(s, c, "%s", "");
> >  }
> >
> > @@ -238,8 +241,9 @@ static void wt_longstatus_print_other_header(struct wt_status *s,
> >         const char *c = color(WT_STATUS_HEADER, s);
> >         status_printf_ln(s, c, "%s:", what);
> >         if (!s->hints)
> > -               return;
> > +               goto conclude;
> >         status_printf_ln(s, c, _("  (use \"git %s <file>...\" to include in what will be committed)"), how);
> > +conclude:
> >         status_printf_ln(s, c, "%s", "");
> >  }
> >
> > --
> > 2.21.0
> >

      reply	other threads:[~2019-04-30  4:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23  9:18 [PATCH] status: add an empty line when there is no hint John Lin
2019-04-30  3:12 ` Phil Hord
2019-04-30  4:46   ` 林自均 [this message]

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='CAKO26MswBM5sjuVSnxssOc4jd+hqXiko=+6ROatOm2H7jndujA@mail.gmail.com' \
    --to=johnlinp@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=phil.hord@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.