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

Re: [PATCH 0 of 7] [resend] - Improve handling remotes, origin, submodules

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 4, 2008, 14:48 UTC
Message-ID
<alpine.LSU.1.00.0802041443420.7372@racer.site>
In-Reply-To
<47A68C01.9000600@gmail.com>
Hi,
On Sun, 3 Feb 2008, Mark Levedahl wrote:
Show 9 quoted lines
> Johannes Schindelin wrote:
> 
> > As far as I understood, your problem was _purely_ a submodule issue.  
> > I find it utterly unnerving that you keep trying to sneak in 
> > _anything_ unrelated to submodules.
>
> It is not purely about submodules, but in fact about a centralized 
> concept (named "origin") disrupting a distributed workflow using 
> submodules in a distributed version control system.

The "origin" concept has nothing to do with a centralised concept. It is there _purely_ for convenience. If you want to fetch/pull from somewhere, you _have_ to specify from where, _except_ if you use the default.

So your argument here is absolutely bogus.
Show 5 quoted lines
> > I am getting pretty angry that you keep trying to complicating things 
> > in that area!
>
> It is easy to substitute emotion for sound technical arguments. Please 
> don't, it helps no one.

I take it very personal if you ignore me and my arguments, so please don't. My apologies for answering emotionally. (I could even say that it is easier to ignore sound technical arguments than to substitute emotion for them.)

My recommendation: fix submodule, and submodule only. For your specific needs. Hint: you do not need to introduce core.origin for that (as should have become totally obvious by now).

Should something like core.origin still be an issue (which I doubt, for the same reason you do not change the _name_ of the environment variable $HOME), we can still continue discussing that.

Hth, Dscho

Previous: Mark LevedahlNext: Mark Levedahl
Message 11 of 19 in “[resend] - Improve handling remotes, origin, submodules”
  1. [resend] - Improve handling remotes, origin, submodulesMark Levedahl, Feb 3, 2008
  2. 1/7 Teach remote machinery about core.origin config variableMark Levedahl, Feb 3, 2008
  3. 2/7 git-remote - Unset core.origin when deleting the default remoteMark Levedahl, Feb 3, 2008
  4. 3/7 git-clone - Set remotes.origin config variableMark Levedahl, Feb 3, 2008
  5. 4/7 git-submodule - Possibly inherit parent's default remote on init/cloneMark Levedahl, Feb 3, 2008
  6. 5/7 Teach git-submodule to use top-level remote when updating subprojectsMark Levedahl, Feb 3, 2008
  7. 6/7 git-submodule - Allow adding a submodule in-placeMark Levedahl, Feb 3, 2008
  8. 7/7 Add t/t7401 - test submodule interaction with remotes machineryMark Levedahl, Feb 3, 2008
  9. Johannes SchindelinFeb 3, 2008
  10. Mark LevedahlFeb 4, 2008
  11. Johannes SchindelinFeb 4, 2008
  12. Mark LevedahlFeb 4, 2008
  13. Johannes SchindelinFeb 4, 2008
  14. Junio C HamanoFeb 4, 2008
  15. Johannes SchindelinFeb 4, 2008
  16. Junio C HamanoFeb 4, 2008
  17. Johannes SchindelinFeb 4, 2008
  18. Steffen ProhaskaFeb 4, 2008
  19. Johannes SchindelinFeb 4, 2008

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.