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, 18:15 UTC
Message-ID
<alpine.LSU.1.00.0802041813110.7372@racer.site>
In-Reply-To
<30e4a070802040924g550671ccsb11108c71c99e378@mail.gmail.com>
Hi,
On Mon, 4 Feb 2008, Mark Levedahl wrote:
Show 5 quoted lines
> On Feb 4, 2008 9:48 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> > 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.

Actually, I said more things. Things about fixing git-submodule first, so that you can ask it to update via different remotes than "origin". And then try to argue for the rest.

Show 8 quoted lines
> BIG difference here:
> $HOME = <name> of home directory, <name> is arbitrary. Files there are
> found as $HOME/<foo> or <name>/foo, they are the same, and I am free
> to set HOME=<arbitrary name>.
> 
> Currently
> $ORIGIN=origin, i.e., the default is *named* origin, not the default
> name is given by $ORIGIN.

"origin" is just the name of the default origin, holding the remote URL. Just like "HOME" is just the name of the variable holding the home directory.

But really.  Fix git-submodule first.

Ciao, Dscho

Previous: Mark LevedahlNext: Junio C Hamano
Message 13 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.