Re: [BUG] Possible bug in `remote set-url --add --push`

2013-01-14 Thread Jardel Weyrich
On 14/01/2013, at 17:09, Junio C Hamano wrote: > Michael J Gruber 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 --a

Re: [BUG] Possible bug in `remote set-url --add --push`

2013-01-12 Thread Jardel Weyrich
On Sat, Jan 12, 2013 at 6:44 AM, Sascha Cunz wrote: > Am Freitag, 11. Januar 2013, 23:10:36 schrieb Junio C Hamano: >> Jardel Weyrich 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). >> &g

Re: [BUG] Possible bug in `remote set-url --add --push`

2013-01-12 Thread Jardel Weyrich
test and test_clone2 (it's a bare repo, sorry for using a misleading name). Is `remote..pushurl` required for the primary URL as well? If not, then git-push is not handling that information as it should. On Sat, Jan 12, 2013 at 5:10 AM, Junio C Hamano wrote: > Jardel Weyrich writes: > >

[BUG] Possible bug in `remote set-url --add --push`

2013-01-11 Thread Jardel Weyrich
Hi, 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 (first URL if no is given) to . If > doe