Re: [RFC/PATCH 0/2] submodule: drop the top-level requirement
- From
Jens Lehmann <jens.lehmann@web.de>
- Date
- Apr 7, 2013, 20:15 UTC
- Message-ID
- <5161D3CB.8090101@web.de>
- In-Reply-To
- <cover.1365364193.git.john@keeping.me.uk>
Am 07.04.2013 21:55, schrieb John Keeping:
Show 10 quoted lines
> With the recent discussion, I wondered how hard it would be to add > SUBDIRECTORY_OK=Yes to git-submodule.sh and it doesn't seem that bad. > > Note that this series currently lacks both tests and documentation > updates. Also I have made no attempt to change the output from any > commands, so submodule paths are always printed relative to the > top-level of the repository. > > Consider this series a proof-of-concept, to see whether I'm on > completely the wrong course.
Cool! Thanks for working on that, I'll take a deeper look in my next Git timeslot.
Show 8 quoted lines
> John Keeping (2): > rev-parse: add --filename-prefix option > submodule: drop the top-level requirement > > builtin/rev-parse.c | 17 ++++++++++++----- > git-submodule.sh | 7 +++++++ > 2 files changed, 19 insertions(+), 5 deletions(-) >