From: "Ping Yin" <pkufranky@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, "Ping Yin" <pkufranky@gmail.com>
Subject: Re: [PATCH v4 2/5] git-submodule summary: show commit summary
Date: Tue, 11 Mar 2008 09:52:13 +0800 [thread overview]
Message-ID: <46dff0320803101852j421646e6t5b8c71b656c72935@mail.gmail.com> (raw)
In-Reply-To: <1205171657-16216-2-git-send-email-pkufranky@gmail.com>
On Tue, Mar 11, 2008 at 1:54 AM, Ping Yin <pkufranky@gmail.com> wrote:
> This patch does the hard work to show submodule commit summary.
>
> For a modified submodule, a series of commits will be shown with
> the following command
>
> git log --pretty='format:%m %s' --left-right \
> --first-parent sha1_src...sha1_dst
>
It seems that --left-right makes no sense when combined with
--pretty='format:%m %s'
I originally thought --left-right will make left-side commits always
appear before or after right side commits, but that's not the case.
Actually it seems that --left-right doesn't influence the commit
order.
Is my understanding right?
> where the src sha1 is from the given super project commit and the
> dst sha1 is from the index or working tree (switched by --cached).
>
--
Ping Yin
next prev parent reply other threads:[~2008-03-11 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 17:54 [PATCH v4 1/5] git-submodule summary: code framework Ping Yin
2008-03-10 17:54 ` [PATCH v4 2/5] git-submodule summary: show commit summary Ping Yin
2008-03-10 17:54 ` [PATCH v4 3/5] git-submodule summary: limit summary size Ping Yin
2008-03-10 17:54 ` [PATCH v4 4/5] git-submodule summary: documentation Ping Yin
2008-03-10 17:54 ` [PATCH v4 5/5] git-submodule summary: test Ping Yin
2008-03-11 1:57 ` Ping Yin
2008-03-10 17:58 ` [PATCH v4 2/5] git-submodule summary: show commit summary Ping Yin
2008-03-11 1:52 ` Ping Yin [this message]
2008-03-11 7:28 ` Junio C Hamano
2008-03-11 9:37 ` 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=46dff0320803101852j421646e6t5b8c71b656c72935@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).