From: Mel Dafert <mel@dafert.at>
To: Philippe Blain <levraiphilippeblain@gmail.com>, git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>,
Ping Yin <pkufranky@gmail.com>
Subject: Re: Bug with branches/merges in submodules
Date: Wed, 14 Jul 2021 13:07:37 +0200 [thread overview]
Message-ID: <6502FFC0-E19B-41FA-B152-885B339360F0@dafert.at> (raw)
In-Reply-To: <b519a79a-5e35-bb40-71d3-0fb3c65320d7@gmail.com>
Hello Philippe,
Thank you for your reply, and the points to the mailing list.
>Thanks for the reproducer. The behaviour for 'git log/show/diff' is due this line
>and the behaviour for 'git submodule summary' to these lines.
>
>For 'git diff' and friends, it goes back to the addition of the '--submodule=log'
>option in 752c0c2492 (Add the --submodule option to the diff option family, 2009-10-19).
>(authored CC'ed). The use of '--first-parent' was discussed on the list
>when this was implemented. I did not read the whole thing.
>
>For 'git submodule summary', it goes back to the addition of the subcommand
>in 1cb639e6b0 (git-submodule summary: show commit summary, 2008-03-11). (author also CC'ed).
>The justification of the use of '--first-parent' was not really discussed
>as far as I could tell.
>
>
>I personnally think it would be a good addition to be able to choose
>if yes or no '--first-parent' should be used
The discussion you found [1] also suggested that as a future option.
In the original implementation, the first mention is [2], where the length of the
message is discussed - I (and later discussions) assume that this just
happened to be the preference of the author.
I would thus like to correct myself, and refile this as a feature request - it would
be very helpful to me to have this as an option, possibly even with one that can be set in the config, similar to
'diff.submodule=log'.
I would be open to implementing this - I might need some mentoring, however, as
this would be my first time contributing (and reading the git codebase).
Regards,
Mel
[1] https://lore.kernel.org/git/67a884457aeaead275612be10902a80726b2a7db.1254668669u.git.johannes.schindelin@gmx.de/t/#u
[2] https://lore.kernel.org/git/46dff0320803061750x70d059a2yaf1e5751e9c62150@mail.gmail.com/
next prev parent reply other threads:[~2021-07-14 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 13:13 Bug with branches/merges in submodules Mel Dafert
2021-07-09 21:18 ` Philippe Blain
2021-07-14 11:07 ` Mel Dafert [this message]
2021-07-14 12:25 ` Philippe Blain
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6502FFC0-E19B-41FA-B152-885B339360F0@dafert.at \
--to=mel@dafert.at \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=levraiphilippeblain@gmail.com \
--cc=pkufranky@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).