From: Antonio Ospite <ao2@ao2.it>
To: git@vger.kernel.org
Cc: Richard Hartmann <richih.mailinglist@gmail.com>,
Antonio Ospite <ao2@ao2.it>
Subject: Re: [RFC 00/10] Make .the gitmodules file path configurable
Date: Fri, 13 Apr 2018 10:07:07 +0200 [thread overview]
Message-ID: <20180413100707.945b38dde1c75ebea8360858@ao2.it> (raw)
In-Reply-To: <20180412222047.5716-1-ao2@ao2.it>
On Fri, 13 Apr 2018 00:20:37 +0200
Antonio Ospite <ao2@ao2.it> wrote:
[...]
> Antonio Ospite (10):
> submodule: add 'core.submodulesFile' to override the '.gitmodules'
> path
> submodule: fix getting custom gitmodule file in fetch command
> submodule: use the 'submodules_file' variable in output messages
> submodule: document 'core.submodulesFile' and fix references to
> '.gitmodules'
> submodule: adjust references to '.gitmodules' in comments
> completion: add 'core.submodulesfile' to the git-completion.bash file
> XXX: wrap-for-bin.sh: set 'core.submodulesFile' for each git
> invocation
> XXX: submodule: fix t1300-repo-config.sh to take into account the new
> config
> XXX: submodule: pass custom gitmodules file to 'test-tool
> submodule-config'
> XXX: add a hacky script to test the changes with a patched test suite
>
I am re-sending the last four highly experimental patches changing the
"XXX" into "FIXME" in the subject lines because vger.kernel.org refused
the original ones with the following message:
The capital Triple-X in subject is way too often associated with junk
email, please rephrase.
Sorry for the inconvenience.
--
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-04-13 8:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 22:20 [RFC 00/10] Make .the gitmodules file path configurable Antonio Ospite
2018-04-12 22:20 ` [RFC 01/10] submodule: add 'core.submodulesFile' to override the '.gitmodules' path Antonio Ospite
2018-04-12 23:50 ` Stefan Beller
2018-04-16 16:37 ` Antonio Ospite
2018-04-16 21:22 ` Stefan Beller
2018-04-18 11:43 ` Antonio Ospite
2018-04-18 18:44 ` Stefan Beller
2018-04-12 22:20 ` [RFC 02/10] submodule: fix getting custom gitmodule file in fetch command Antonio Ospite
2018-04-12 23:55 ` Stefan Beller
2018-04-16 16:18 ` Antonio Ospite
2018-04-16 19:23 ` Stefan Beller
2018-04-16 20:46 ` Antonio Ospite
2018-04-12 22:20 ` [RFC 03/10] submodule: use the 'submodules_file' variable in output messages Antonio Ospite
2018-04-12 22:20 ` [RFC 04/10] submodule: document 'core.submodulesFile' and fix references to '.gitmodules' Antonio Ospite
2018-04-12 22:20 ` [RFC 05/10] submodule: adjust references to '.gitmodules' in comments Antonio Ospite
2018-04-12 22:20 ` [RFC 06/10] completion: add 'core.submodulesfile' to the git-completion.bash file Antonio Ospite
2018-04-12 23:36 ` [RFC 00/10] Make .the gitmodules file path configurable Stefan Beller
2018-04-16 11:33 ` Antonio Ospite
2018-04-16 19:22 ` Stefan Beller
2018-04-13 8:07 ` Antonio Ospite [this message]
2018-04-13 8:07 ` [RFC 07/10] FIXME: wrap-for-bin.sh: set 'core.submodulesFile' for each git invocation Antonio Ospite
2018-04-13 8:07 ` [RFC 08/10] FIXME: submodule: fix t1300-repo-config.sh to take into account the new config Antonio Ospite
2018-04-13 8:07 ` [RFC 09/10] FIXME: submodule: pass custom gitmodules file to 'test-tool submodule-config' Antonio Ospite
2018-04-13 8:07 ` [RFC 10/10] FIXME: add a hacky script to test the changes with a patched test suite Antonio Ospite
2018-04-13 20:05 ` [RFC 07/10] FIXME: wrap-for-bin.sh: set 'core.submodulesFile' for each git invocation Stefan Beller
2018-04-16 11:36 ` Antonio Ospite
2018-04-23 17:47 ` [RFC 00/10] Make .the gitmodules file path configurable Jonathan Nieder
2018-04-30 12:51 ` Antonio Ospite
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=20180413100707.945b38dde1c75ebea8360858@ao2.it \
--to=ao2@ao2.it \
--cc=git@vger.kernel.org \
--cc=richih.mailinglist@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).