On Mon, Mar 30, 2015 at 12:39:17PM -0700, Junio C Hamano wrote:
> Whichever way you implement "remote rename", you will make half of
> the users happy while making other half unhappy. One use case will
> be happier if remote.pushdefault is left intact; the other use case
> will be happier if remo
Alexander Duytschaever writes:
> When defining pushdefault and renaming the associated remote, the
> pushdefault setting becomes invalid. Instead, it should follow the
> renamed remote if that was designated as pushdefault.
>
> Test procedure:
>
> 1. Create/cd empty directory
> 2. `git init .`
>
When defining pushdefault and renaming the associated remote, the pushdefault
setting becomes invalid. Instead, it should follow the renamed remote if that
was designated as pushdefault.
Test procedure:
1. Create/cd empty directory
2. `git init .`
3. `git remote add abc def`
4. Observe that `gi
3 matches
Mail list logo
