From: "Ping Yin" <pkufranky@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 2/5] git-submodule summary: show commit summary
Date: Tue, 11 Mar 2008 17:37:40 +0800 [thread overview]
Message-ID: <46dff0320803110237t6fcd6675t48949423e14f64a5@mail.gmail.com> (raw)
In-Reply-To: <7vod9ld8iu.fsf@gitster.siamese.dyndns.org>
On Tue, Mar 11, 2008 at 3:28 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Ping Yin <pkufranky@gmail.com> writes:
>
> > This patch does the hard work to show submodule commit summary.
> > ...
>
> I've spent considerable amount of time cleaning up your commit log
> messages for the entire series from the last round when I queued them to
> 'pu', but you seem to have discarded all of them. As I do not have time
> to waste doing clean-ups only to have others to discard, and I do not have
> infinite amount of time, I won't be replacing them with this series
> tonight.
>
Sorry about this. This is my first big patch series and I have little
experience about submiting patches again and again. So i don't even
see your pu series except the documentation one you have mentioned in
the email (I thought other ones didn't change).
I'll resend my patches finally merging you commit log.
>
> > Signed-off-by: Ping Yin <pkufranky@gmail.com>
>
> And you did not describe anything about the improvements from the previous
> round anywhere. interdiff shows that this part is somewhat different:
>
>
> > + then
> > + case "$mod_dst" in
> > + 160000)
> > + sha1_dst=$(GIT_DIR="$name/.git" git rev-parse HEAD)
> > + ;;
> > + 100644)
> > + sha1_dst=$(git hash-object $name)
> > + ;;
> > + esac
>
> Earlier, you were ignoring the one that is not checked out anymore, but
> now you blindly assume "rev-parse HEAD" to give you a usable sha1_dst.
> Why?
The path will not reach here for ignored submodules. Only user-cared
modules will get into the "$modules" variables (see "# Get modified
modules cared by user" part).
>
> If a path that previously was a module is changed to a symlink, what
> happens?
>
--
Ping Yin
prev parent reply other threads:[~2008-03-11 9:38 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
2008-03-11 7:28 ` Junio C Hamano
2008-03-11 9:37 ` 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=46dff0320803110237t6fcd6675t48949423e14f64a5@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).