Skip to content

Loading…

Be protocol-agnostic wrt/ Git URL's #360

Open
wants to merge 1 commit into from

2 participants

@asnowfix

Today's sub-module URL scheme is git:// regardless of whether the top-
level (gitflow) repository. is SSH (git@github:...), HTTPS
(https://) or Git socket (git://).

This small change uses relative URL's for sub-modules & hence re-use
the top-level repo URL model for the sub-module.

@asnowfix asnowfix Be protocol-agnostic wrt/ Git URL's
Today's sub-module URL scheme is `git://` regardless of whether the top-
level (gitflow) repository.  is SSH (`git@github:...), HTTPS
(`https://`) or Git socket (`git://`).

This small change uses relative URL's for sub-modules & hence re-use
the top-level repo URL model for the sub-module.
bb5e300
@petervanderdoes

Not likely to be merged, last commit on the repo was 2 years ago.

You might want to check git-flow AVH Edition. Checkout the changelog for more information about bugfixes and new features implemented.

Disclaimer: I'm the project lead for git-flow AVH Edition

@asnowfix

Thanks for the heads-up @petervanderdoes .

@asnowfix

@petervanderdoes I was about to submit my PR to your fork, but it turns out that it was already implemented. I'll let this PR here just in case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Apr 23, 2014
  1. @asnowfix

    Be protocol-agnostic wrt/ Git URL's

    asnowfix committed
    Today's sub-module URL scheme is `git://` regardless of whether the top-
    level (gitflow) repository.  is SSH (`git@github:...), HTTPS
    (`https://`) or Git socket (`git://`).
    
    This small change uses relative URL's for sub-modules & hence re-use
    the top-level repo URL model for the sub-module.
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 1 deletion.
  1. +1 −1 .gitmodules
View
2 .gitmodules
@@ -1,3 +1,3 @@
[submodule "shFlags"]
path = shFlags
- url = git://github.com/nvie/shFlags.git
+ url = ../shFlags.git
Something went wrong with that request. Please try again.