From: "Ping Yin" <pkufranky@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 2/4] git-submodule: New subcommand 'summary' (2) - show commit summary
Date: Thu, 6 Mar 2008 10:16:23 +0800 [thread overview]
Message-ID: <46dff0320803051816x5b957da0m6396d31cad8b4116@mail.gmail.com> (raw)
In-Reply-To: <7vk5kgiv0v.fsf@gitster.siamese.dyndns.org>
On Thu, Mar 6, 2008 at 7:57 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Ping Yin <pkufranky@gmail.com> writes:
>
> > Example: commit summary for modified submodules sm1-sm5.
> > --A-->B-->C (in src:354cd45)
> > \
> > -->D-->E (in dst:3f751e5)
>
> The ordering of the commits in the above list is (1) unnatural and (2)
> does not match what you would see with "log --left-right --topo-order
> C...E".
>
> I do not think "it shows the path to move from C to E" justifies it. If
> you are showing them as a linear list (which you cannot avoid if you are
> doing a sequence of one-line description), you cannot represent such a
> "path" anyway (think "merge"). If an appliance project rebinds kernel/
> path from a project based on linux-2.4 to linux-2.6 while upgrading, such
> a "path" may not even exist.
>
Good point to show 'log --left-right --topo-order' is better
> I think I've already said the above to your initial round. It is a bit
> dissapointing to see none of the comments were addressed and makes me
> wonder if I have wasted my time reviewing them again.
Sorry i lost your comments. Maybe it's a long time ago, i will revisit them.
>
> It also is unnerving that newly added and deleted submodule results in the
> full history display. It would be assuring to be able to see and verify
> what the top commit is (or was in "deleted" case) while you are commiting,
> but I do not see a reason to show more than that.
>
> I do not think "then set the limit to 1" is a valid answer to that
> concern. Wanting to see a dozen top commits in each for a modified
> submodule would be sensible (and 3/4 may implement such a limit) but even
> then showing dozen top commits for new/deleted at the same time would be
> just an added noise. Is it really necessary to show more than the top for
> new/deleted case?
>
Actually, not make much sense to show many commits in delete or add
case. I think showing 2 (the head and tail one) should make more sense
since the head one would be "Initial add ..." in many cases which
doesn't make much sense for the user.
I will resend my patches after taking considering all of your
suggestion today or tommorow.
--
Ping Yin
next prev parent reply other threads:[~2008-03-06 2:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 18:15 [PATCH v3 1/4] git-submodule: New subcommand 'summary' (1) - code framework Ping Yin
2008-03-02 18:15 ` [PATCH v3 2/4] git-submodule: New subcommand 'summary' (2) - show commit summary Ping Yin
2008-03-05 23:57 ` Junio C Hamano
2008-03-06 2:16 ` Ping Yin [this message]
2008-03-06 4:10 ` Junio C Hamano
2008-03-06 5:56 ` Ping Yin
2008-03-06 10:42 ` Junio C Hamano
2008-03-06 11:36 ` Ping Yin
2008-03-02 18:15 ` [PATCH v3 3/4] git-submodule: New subcommand 'summary' (3) - limit summary size Ping Yin
2008-03-06 0:24 ` Junio C Hamano
2008-03-06 2:24 ` Ping Yin
2008-03-07 1:50 ` Ping Yin
2008-03-02 18:15 ` [PATCH v3 4/4] git-submodule: New subcommand 'summary' (4) - Update the document Ping Yin
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=46dff0320803051816x5b957da0m6396d31cad8b4116@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).