From: Antonio Ospite <ao2@ao2.it>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)
Date: Sat, 15 Sep 2018 22:17:43 +0200 [thread overview]
Message-ID: <20180915221743.a018386eb34f6ac792c6e694@ao2.it> (raw)
In-Reply-To: <xmqqy3c3agkr.fsf@gitster-ct.c.googlers.com>
On Fri, 14 Sep 2018 14:56:36 -0700
Junio C Hamano <gitster@pobox.com> wrote:
[...]
> * ao/submodule-wo-gitmodules-checked-out (2018-08-14) 7 commits
> - submodule: support reading .gitmodules even when it's not checked out
> - t7506: clean up .gitmodules properly before setting up new scenario
> - submodule: use the 'submodule--helper config' command
> - submodule--helper: add a new 'config' subcommand
> - t7411: be nicer to future tests and really clean things up
> - submodule: factor out a config_set_in_gitmodules_file_gently function
> - submodule: add a print_config_from_gitmodules() helper
>
> The submodule support has been updated to read from the blob at
> HEAD:.gitmodules when the .gitmodules file is missing from the
> working tree.
>
> Expecting a reroll.
>
> I find the design a bit iffy in that our usual "missing in the
> working tree? let's use the latest blob" fallback is to take it
> from the index, not from the HEAD.
>
Hi Junio,
I did send a v4 addressing this:
https://public-inbox.org/git/20180824132951.8000-1-ao2@ao2.it/
In case you missed it I might as well send a v5 with some minor
cosmetic touches suggested by Ævar:
https://public-inbox.org/git/87wosfesxl.fsf@evledraar.gmail.com/
Ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
next prev parent reply other threads:[~2018-09-15 20:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 21:56 What's cooking in git.git (Sep 2018, #03; Fri, 14) Junio C Hamano
2018-09-15 20:17 ` Antonio Ospite [this message]
2018-09-17 15:11 ` Junio C Hamano
2018-09-16 6:39 ` Duy Nguyen
2018-09-16 15:09 ` Ævar Arnfjörð Bjarmason
2018-09-17 2:39 ` Jeff King
2018-09-17 17:51 ` Junio C Hamano
2018-09-17 18:22 ` Jeff King
2018-09-17 18:26 ` Jonathan Nieder
2018-09-16 12:01 ` brian m. carlson
2018-09-17 15:10 ` Junio C Hamano
2018-09-17 18:35 ` Derrick Stolee
2018-09-17 19:04 ` Junio C Hamano
2018-09-17 22:54 ` Junio C Hamano
2018-09-19 3:49 ` [PATCH] pack-objects: handle island check for "external" delta base Jeff King
2018-09-19 18:34 ` Martin Ågren
2018-09-19 18:43 ` Jeff King
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=20180915221743.a018386eb34f6ac792c6e694@ao2.it \
--to=ao2@ao2.it \
--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.
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).