Thread (24 messages) flat view 24 messages, 6 authors, 2016-06-15
STALE3724d

Revision rfc of 4 in this series.

Revisions (4)
  1. rfc current
  2. v2 [diff vs current]
  3. v3 [diff vs current]
  4. v4 [diff vs current]

[RFC/PATCH 0/2] submodule: drop the top-level requirement

From: John Keeping <hidden>
Date: 2016-06-15 22:56:43

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.

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(-)

-- 
1.8.2.694.ga76e9c3.dirty
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help