On 12-07-11 05:55 PM, Junio C Hamano wrote:
> Marc Branchaud writes:
>
>> What about a warning displayed if "remote.default" is not set? Something
>> like:
>>
>> This repository does not have an explicitly configured default
>> remote. Selecting "origin" as the default remote reposit
Marc Branchaud writes:
> What about a warning displayed if "remote.default" is not set? Something
> like:
>
> This repository does not have an explicitly configured default
> remote. Selecting "origin" as the default remote repository.
> To suppress this warning, or if you wi
On 12-07-11 02:27 PM, Junio C Hamano wrote:
> marcn...@xiplink.com writes:
>
>> From: Marc Branchaud
>>
>> The "rename" and "rm" commands now handle the case where the remote being
>> changed is the default remote.
>
> "handle the case" is way underspecified.
>
> Until I peeked the patch, I cou
marcn...@xiplink.com writes:
> From: Marc Branchaud
>
> The "rename" and "rm" commands now handle the case where the remote being
> changed is the default remote.
"handle the case" is way underspecified.
Until I peeked the patch, I couldn't tell if you were now allowing
"git remote rm" that doe
From: Marc Branchaud
The "rename" and "rm" commands now handle the case where the remote being
changed is the default remote.
If the "add" command is used to add the repo's first remote, that remote
becomes the default remote.
Also introduce a "default" sub-command to get or set the default rem
5 matches
Mail list logo