git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ping Yin" <pkufranky@gmail.com>
To: "Johannes Sixt" <j.sixt@viscovery.net>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH v2 0/5] builtin-status submodule summary
Date: Sat, 15 Mar 2008 01:42:57 +0800	[thread overview]
Message-ID: <46dff0320803141042g561f94aen2bf8396a2766054b@mail.gmail.com> (raw)
In-Reply-To: <47DAA638.6060108@viscovery.net>

On Sat, Mar 15, 2008 at 12:22 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Ping Yin schrieb:
>
> > IMO, git submodule summary is not so useful for me if it's not
>  > integrated into git-status. In fact i never use "git submodule
>  > summary" directly. git-status with submodule summary support is very
>  > useful to help user figure out what is going on in a more global level
>  > when cooking the commit message.
>  >
>  > So i think this series should go along with the submodule summary series.
>
>  I think so, too. The changes and defaults in wt-status.c are trivial
>  enough that they don't penalize traditional git-status users.
>
>
>  > The v2 series has following commits adding a new commit for documentation
>  >
>  >     1  git-submodule summary: --for-status option
>  >     2  builtin-status: submodule summary support
>  >     3  builtin-status: configurable submodule summary size
>  >     4  buitin-status: Add tests for submodule summary
>  >     5  git-status: Mention status.submodulesummary config in the documentation
>
>  I'd actually squash 2, 3, and 5.
>
>  You still have the statement before a declaration in 3/5.
Sorry i forgot about it.

>
>
>  > +     if (! wt_status_submodule_summary) return;
>
>  And here the important part (IMO) is actually that 'return' should go on a
>  line of its own.
OK



-- 
Ping Yin

      reply	other threads:[~2008-03-14 17:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 15:28 [PATCH v2 0/5] builtin-status submodule summary Ping Yin
2008-03-14 15:28 ` [PATCH v2 1/5] git-submodule summary: --for-status option Ping Yin
2008-03-14 15:28   ` [PATCH v2 2/5] builtin-status: submodule summary support Ping Yin
2008-03-14 15:28     ` [PATCH v2 3/5] builtin-status: configurable submodule summary size Ping Yin
2008-03-14 15:28       ` [PATCH v2 4/5] buitin-status: Add tests for submodule summary Ping Yin
2008-03-14 15:28         ` [PATCH v2 5/5] git-status: Mention status.submodulesummary config in the documentation Ping Yin
2008-03-14 16:22 ` [PATCH v2 0/5] builtin-status submodule summary Johannes Sixt
2008-03-14 17:42   ` Ping Yin [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=46dff0320803141042g561f94aen2bf8396a2766054b@mail.gmail.com \
    --to=pkufranky@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    /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 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).