From: "Ping Yin" <pkufranky@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: builtin-status submodule summary
Date: Sat, 15 Mar 2008 01:45:15 +0800 [thread overview]
Message-ID: <46dff0320803141045w5cf1506fw9ab676f041a4bd12@mail.gmail.com> (raw)
In-Reply-To: <7vprtxp8ew.fsf@gitster.siamese.dyndns.org>
On Sat, Mar 15, 2008 at 12:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
> "Ping Yin" <pkufranky@gmail.com> writes:
>
> > So i think this series should go along with the submodule summary series.
>
>
> Recall how many rounds "submodule summary" took to get into that state,
> and how much time and effort were spent on it. Use it as a yardstick to
> guesstimate how much further effort and time will be needed to get the
> changes to git-status into a reasonable shape.
>
> It may happen eventually, but not before 1.5.5.
>
So i'll resend my patches considering suggestions from Johannes Sixt
after 1.5.5.
--
Ping Yin
prev parent reply other threads:[~2008-03-14 17:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 13:48 builtin-status submodule summary Ping Yin
2008-03-13 13:48 ` [PATCH v2 1/4] git-submodule summary: --for-status option Ping Yin
2008-03-13 13:48 ` [PATCH v2 2/4] builtin-status: submodule summary support Ping Yin
2008-03-13 13:48 ` [PATCH v2 3/4] builtin-status: configurable submodule summary size Ping Yin
2008-03-13 13:48 ` [PATCH v2 4/4] buitin-status: Add tests for submodule summary Ping Yin
2008-03-13 14:21 ` Johannes Sixt
2008-03-13 18:04 ` Junio C Hamano
2008-03-13 18:14 ` Ping Yin
2008-03-13 18:09 ` Ping Yin
2008-03-13 14:15 ` [PATCH v2 3/4] builtin-status: configurable submodule summary size Johannes Sixt
2008-03-13 14:11 ` [PATCH v2 2/4] builtin-status: submodule summary support Johannes Sixt
2008-03-13 18:01 ` Ping Yin
2008-03-14 14:30 ` builtin-status submodule summary Ping Yin
2008-03-14 16:39 ` Junio C Hamano
2008-03-14 17:45 ` 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=46dff0320803141045w5cf1506fw9ab676f041a4bd12@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--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.
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).