Junio C Hamano venit, vidit, dixit 15.01.2013 16:53:
Michael J Gruber g...@drmicha.warpmail.net writes:
Also there is a conceptual confusion: pushurl is meant to push to the
same repo using a different url, e.g. something authenticated
(https/ssh) for push and something faster/easier for
Michael J Gruber g...@drmicha.warpmail.net writes:
Junio C Hamano venit, vidit, dixit 15.01.2013 16:53:
...
* When there are more than one URLs, and there is no pushURL, then
show the first URL as (fetch/push), and the remainder in a
notation that says it is used only for push, but it
On Tue, Jan 15, 2013 at 10:53 AM, Junio C Hamano gits...@pobox.com wrote:
Michael J Gruber g...@drmicha.warpmail.net writes:
That being said, I don't mind changing the behaviour of set-url.
I do not think we want to change the behaviour of set-url.
I agree with Michael that changing the
Junio C Hamano venit, vidit, dixit 16.01.2013 16:50:
Michael J Gruber g...@drmicha.warpmail.net writes:
Junio C Hamano venit, vidit, dixit 15.01.2013 16:53:
...
* When there are more than one URLs, and there is no pushURL, then
show the first URL as (fetch/push), and the remainder in a
Phil Hord venit, vidit, dixit 16.01.2013 17:15:
On Tue, Jan 15, 2013 at 10:53 AM, Junio C Hamano gits...@pobox.com wrote:
Michael J Gruber g...@drmicha.warpmail.net writes:
That being said, I don't mind changing the behaviour of set-url.
I do not think we want to change the behaviour of
Junio C Hamano gits...@pobox.com writes:
I actually think my earlier it shouldn't be the same (push) is not
needed and probably is actively wrong. Just like you can tell
between
(only one .url) (both .url and .pushurl)
origin there (fetch/push) origin
Andreas Schwab sch...@linux-m68k.org writes:
Junio C Hamano gits...@pobox.com writes:
I actually think my earlier it shouldn't be the same (push) is not
needed and probably is actively wrong. Just like you can tell
between
(only one .url) (both .url and .pushurl)
response
From: Jardel Weyrich jweyr...@gmail.com
Subject: Re: [BUG] Possible bug in `remote set-url --add --push`
Date: Sat, 12 Jan 2013 06:09:35 -0200
Message-ID:
can8taovp_hx6bek86ayox-kvqwdmsbyptxtt2nk+fx+ut1t...@mail.gmail.com
where you showed that there was only
Jardel Weyrich venit, vidit, dixit 12.01.2013 10:33:
On Sat, Jan 12, 2013 at 6:44 AM, Sascha Cunz sascha...@babbelbox.org wrote:
Am Freitag, 11. Januar 2013, 23:10:36 schrieb Junio C Hamano:
Jardel Weyrich jweyr...@gmail.com writes:
I believe `remote set-url --add --push` has a bug. Performed
Michael J Gruber g...@drmicha.warpmail.net writes:
It seems to me that everything works as designed, and that the man page
talk about push URLs can be read in two ways,...
Hmph, but I had an impression that Jardel's original report was that
one of the --add --pushurl was not adding but was
On 14/01/2013, at 17:09, Junio C Hamano gits...@pobox.com wrote:
Michael J Gruber g...@drmicha.warpmail.net writes:
It seems to me that everything works as designed, and that the man page
talk about push URLs can be read in two ways,...
Hmph, but I had an impression that Jardel's original
Jardel Weyrich jweyr...@gmail.com writes:
If you allow me, I'd like you to forget about the concepts for a minute, and
focus on the user experience.
Imagine a simple hypothetical scenario in which the user wants to push to 2
distinct repositories. He already has cloned the repo from the 1st
...@gmail.com
Subject: Re: [BUG] Possible bug in `remote set-url --add --push`
Date: Sat, 12 Jan 2013 06:09:35 -0200
Message-ID:
can8taovp_hx6bek86ayox-kvqwdmsbyptxtt2nk+fx+ut1t...@mail.gmail.com
where you showed that there was only remote.origin.url (and no
pushurl) in the first step
Step 1:
jweyrich@pharao:test_clone1 [* master]$ git remote -v
origin /Volumes/sandbox/test (fetch)
origin /Volumes/sandbox/test (push)
jweyrich@pharao:test_clone1 [* master]$ git config -l | grep '^remote\.origin'
remote.origin.url=/Volumes/sandbox/test
Jardel Weyrich jweyr...@gmail.com writes:
Step 1:
jweyrich@pharao:test_clone1 [* master]$ git remote -v
origin /Volumes/sandbox/test (fetch)
origin /Volumes/sandbox/test (push)
jweyrich@pharao:test_clone1 [* master]$ git config -l | grep '^remote\.origin'
Am Freitag, 11. Januar 2013, 23:10:36 schrieb Junio C Hamano:
Jardel Weyrich jweyr...@gmail.com writes:
I believe `remote set-url --add --push` has a bug. Performed tests
with v1.8.0.1 and v1.8.1 (Mac OS X).
Quoting the relevant part of the documentation:
set-url
Changes URL
On Sat, Jan 12, 2013 at 6:44 AM, Sascha Cunz sascha...@babbelbox.org wrote:
Am Freitag, 11. Januar 2013, 23:10:36 schrieb Junio C Hamano:
Jardel Weyrich jweyr...@gmail.com writes:
I believe `remote set-url --add --push` has a bug. Performed tests
with v1.8.0.1 and v1.8.1 (Mac OS X).
Jardel Weyrich jweyr...@gmail.com writes:
I believe `remote set-url --add --push` has a bug. Performed tests
with v1.8.0.1 and v1.8.1 (Mac OS X).
Quoting the relevant part of the documentation:
set-url
Changes URL remote points to. Sets first URL remote points to matching
regex
18 matches
Mail list logo
