From: Mark Levedahl <mlevedahl@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH 0 of 7] [resend] - Improve handling remotes, origin, submodules
Date: Sun, 03 Feb 2008 22:52:33 -0500 [thread overview]
Message-ID: <47A68C01.9000600@gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0802032237320.7372@racer.site>
Johannes Schindelin wrote:
> Hi,
>
> 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.
> 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.
Mark
next prev parent reply other threads:[~2008-02-04 3:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 17:31 [PATCH 0 of 7] [resend] - Improve handling remotes, origin, submodules Mark Levedahl
2008-02-03 17:31 ` [PATCH 1/7] Teach remote machinery about core.origin config variable Mark Levedahl
2008-02-03 17:31 ` [PATCH 2/7] git-remote - Unset core.origin when deleting the default remote Mark Levedahl
2008-02-03 17:31 ` [PATCH 3/7] git-clone - Set remotes.origin config variable Mark Levedahl
2008-02-03 17:31 ` [PATCH 4/7] git-submodule - Possibly inherit parent's default remote on init/clone Mark Levedahl
2008-02-03 17:31 ` [PATCH 5/7] Teach git-submodule to use top-level remote when updating subprojects Mark Levedahl
2008-02-03 17:31 ` [PATCH 6/7] git-submodule - Allow adding a submodule in-place Mark Levedahl
2008-02-03 17:31 ` [PATCH 7/7] Add t/t7401 - test submodule interaction with remotes machinery Mark Levedahl
2008-02-03 22:43 ` [PATCH 0 of 7] [resend] - Improve handling remotes, origin, submodules Johannes Schindelin
2008-02-04 3:52 ` Mark Levedahl [this message]
2008-02-04 14:48 ` Johannes Schindelin
2008-02-04 17:24 ` Mark Levedahl
2008-02-04 18:15 ` Johannes Schindelin
2008-02-04 19:59 ` Junio C Hamano
2008-02-04 20:47 ` Johannes Schindelin
2008-02-04 21:40 ` Junio C Hamano
2008-02-04 21:49 ` Johannes Schindelin
2008-02-04 5:19 ` Steffen Prohaska
2008-02-04 14:55 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A68C01.9000600@gmail.com \
--to=mlevedahl@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).