git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: serving git with both "git:" and "http:" and submodules

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 14, 2010, 15:39 UTC
Message-ID
<20100714153900.GB1583@burratino>
In-Reply-To
<4C3DD7EF.6010805@panasas.com>
Boaz Harrosh wrote:
Show 9 quoted lines
> So smart people using git will just do:
> 1. $ git clone git://my-domain.org/my-tree/.git
> 2. $ git submodule init
> 3. $ git submodule update
> 
> And all is well... But smart ass corporate people would not use "git:"
> protocol because of fire-walls and for them I have a dumb "http:" export
> as:
> 1. $ git clone http://my-domain.org/trees/my-tree/.git
[...]
> So my question is: Can I automate this so people with "http:"
> clones are not forced to manually edit their config files?
> (Some users are just not up to it)

Sure. For example, you can ship an update-submodules.sh script to take care of checking “git config remote.origin.url” and updating the ‘[submodule "sub"] url’ configuration to match.

Of course, even this would not make 'git clone --recursive http://my-domain.org/trees/my-tree/.git' work. If you can get git-http-backend working, I’d suggest using that so you only have to deal with one url.

Hope that helps, Jonathan

Previous: Boaz HarroshNext: Boaz Harrosh
Message 2 of 12 in “serving git with both "git:" and "http:" and submodules”
  1. Boaz HarroshJul 14, 2010
  2. Jonathan NiederJul 14, 2010
  3. Boaz HarroshJul 14, 2010
  4. Jonathan NiederJul 14, 2010
  5. Brad KingJul 15, 2010
  6. Peter KreftingJul 15, 2010
  7. gitmodules.5: url can be a relative pathJonathan Nieder, Jul 15, 2010
  8. Documentation: add submodule.* to the big configuration variable listJonathan Nieder, Jul 15, 2010
  9. Johan HerlandJul 15, 2010
  10. Jonathan NiederJul 15, 2010
  11. Johan HerlandJul 15, 2010
  12. Boaz HarroshJul 15, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.