From: Stephen Kelly <steveire@gmail.com>
To: git@vger.kernel.org
Subject: Re: gitk with submodules does not show new commits on other branches
Date: Tue, 24 Jun 2014 12:07:03 +0200 [thread overview]
Message-ID: <lobik7$a7b$1@ger.gmane.org> (raw)
In-Reply-To: 53A88067.5010908@web.de
Jens Lehmann wrote:
> Am 23.06.2014 20:24, schrieb Stephen Kelly:
>> Stephen Kelly wrote:
>>
>>> I see that gitk is showing the output of git diff --submodule, similar
>>> to git submodule summary.
>
> Right, and for your use case --submodule would have to learn a
> different value in addition to 'log' and 'short'. And the default
> is already configurable via the 'diff.submodule' config option.
Right.
>>> Assuming that is not going to be changed, maybe I can hack
>>> parseblobdiffline locally. I have not really tried to read of write tcl
>>> code before though, so I'd still prefer a 'proper' solution somehow.
>
> I'd prefer a proper solution too, which is exactly why I tried
> to understand your use case first before speculating about how
> it could be solved.
Thanks for your help!
>> I dug deeper and came up with this patch which suits my needs:
>
> Yup, I think that's the core of the change necessary to help
> your workflow.
Ok, so I guess we can add --summary=commits ?
I don't write C code generally, so I'm not certain how that needs to be
propagated.
Thanks,
Steve.
prev parent reply other threads:[~2014-06-24 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 14:09 gitk with submodules does not show new commits on other branches Stephen Kelly
2014-06-22 15:42 ` Jens Lehmann
2014-06-22 15:45 ` Stephen Kelly
2014-06-23 13:25 ` Stephen Kelly
2014-06-23 16:31 ` Jens Lehmann
2014-06-23 16:54 ` Stephen Kelly
2014-06-23 17:00 ` Stephen Kelly
2014-06-23 17:35 ` Stephen Kelly
2014-06-23 18:24 ` Stephen Kelly
2014-06-23 19:30 ` Jens Lehmann
2014-06-24 10:07 ` Stephen Kelly [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='lobik7$a7b$1@ger.gmane.org' \
--to=steveire@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.