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

Hi,

On Sun, 3 Feb 2008, Mark Levedahl wrote:

Johannes Schindelin wrote:

quoted

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.

quoted

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