From: Junio C Hamano <gitster@pobox•com>
To: Robert Dailey <rcdailey.lists@gmail•com>
Cc: Heiko Voigt <hvoigt@hvoigt•net>,
Jonathan Nieder <jrnieder@gmail•com>, Git <git@vger•kernel.org>,
Jens Lehmann <Jens.Lehmann@web•de>
Subject: Re: Relative submodule URLs
Date: Tue, 19 Aug 2014 09:39:08 -0700 [thread overview]
Message-ID: <xmqqiolowi1f.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAHd499CJfX_n_KnQScTFueCSkj6i0x0ozwwD8Oe_2a-VH2oq1w@mail.gmail.com> (Robert Dailey's message of "Tue, 19 Aug 2014 11:15:24 -0500")
Robert Dailey <rcdailey.lists@gmail•com> writes:
> The way I set up my remote tracking branch will be different for each
> of these commands:
>
> - git pull :: If I want convenient pulls (with rebase), I will track
> my upstream branch. My pushes have to be more explicit as a tradeoff.
Keeping 'origin' pointing at the repository where you cloned from,
without doing anything funky (i.e. "set up my remote") would give
you convenient pulls.
> - git push :: If I want convenient pushes, track my origin branch.
> Pulls become less convenient. My relative submodules will now need to
> be forked.
You need to configure your pushes to go to a different place, if you
want them to go to a different place ;-).
Long time ago, it used to be that you have to affect the URL used in
both direction, making pulls less conveninent, but hasn't this been
made an non-issue for triangular workflows with the introduction of
remote.pushdefault long time ago?
> - git submodule update :: I track upstream to avoid forking my
> submodules. But pushes become more inconvenient.
If 'submodule update' follows the same place as 'pull' goes by
default, I would imagine that there is no issue here, no? Am I
oversimplifying the issue by guessing that the root cause of is that
you are not using remote.pushdefault from your configuration
toolchest and instead setting the 'origin' to a wrong (i.e. where
push goes) place?
next prev parent reply other threads:[~2014-08-19 16:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 18:22 Relative submodule URLs Robert Dailey
2014-08-18 20:55 ` Jonathan Nieder
2014-08-19 10:24 ` Heiko Voigt
2014-08-19 16:15 ` Robert Dailey
2014-08-19 16:39 ` Junio C Hamano [this message]
2014-08-19 16:50 ` Robert Dailey
2014-08-19 19:19 ` Junio C Hamano
2014-08-19 20:18 ` Robert Dailey
2014-08-19 19:30 ` Heiko Voigt
2014-08-19 20:23 ` Robert Dailey
2014-08-19 20:57 ` Heiko Voigt
2014-08-20 13:18 ` Robert Dailey
2014-08-21 12:37 ` Heiko Voigt
2014-08-19 16:07 ` Robert Dailey
2014-08-22 16:00 ` Marc Branchaud
2014-08-24 13:34 ` Heiko Voigt
2014-08-25 14:29 ` Robert Dailey
2014-08-25 14:32 ` Robert Dailey
2014-08-26 6:28 ` Heiko Voigt
2014-08-26 15:18 ` Robert Dailey
2014-08-26 20:34 ` Heiko Voigt
2014-08-25 13:48 ` Robert Dailey
2014-08-28 17:44 ` Marc Branchaud
2014-08-28 19:35 ` Heiko Voigt
2014-08-29 15:09 ` Marc Branchaud
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=xmqqiolowi1f.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Jens.Lehmann@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=hvoigt@hvoigt$(echo .)net \
--cc=jrnieder@gmail$(echo .)com \
--cc=rcdailey.lists@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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