Re: branch --set-upstream-to unexpectedly fails with "starting point ... is no branch"

2015-11-25 Thread Marc Strapetz
On 24.11.2015 17:58, Carlos Martín Nieto wrote: On 23 Nov 2015, at 19:59, Marc Strapetz wrote: On 23.11.2015 18:04, Carlos Martín Nieto wrote: Hello Mark, On 23 Nov 2015, at 12:04, Marc Strapetz wrote: There is a strange "branch

Re: branch --set-upstream-to unexpectedly fails with "starting point ... is no branch"

2015-11-24 Thread Carlos Martín Nieto
On 23 Nov 2015, at 19:59, Marc Strapetz wrote: > On 23.11.2015 18:04, Carlos Martín Nieto wrote: >> Hello Mark, >> >> On 23 Nov 2015, at 12:04, Marc Strapetz wrote: >> >>> There is a strange "branch --set-upstream-to" failure for "clones"

branch --set-upstream-to unexpectedly fails with "starting point ... is no branch"

2015-11-23 Thread Marc Strapetz
There is a strange "branch --set-upstream-to" failure for "clones" which haven't been created using "git clone" but constructed using "git init", "git remote add" and "git fetch". Following script first creates a "main" repository and then constructs the clone. Finally, in the clone branches

Re: branch --set-upstream-to unexpectedly fails with "starting point ... is no branch"

2015-11-23 Thread Marc Strapetz
On 23.11.2015 18:04, Carlos Martín Nieto wrote: Hello Mark, On 23 Nov 2015, at 12:04, Marc Strapetz wrote: There is a strange "branch --set-upstream-to" failure for "clones" which haven't been created using "git clone" but constructed using "git init", "git remote

Re: branch --set-upstream-to unexpectedly fails with "starting point ... is no branch"

2015-11-23 Thread Carlos Martín Nieto
Hello Mark, On 23 Nov 2015, at 12:04, Marc Strapetz wrote: > There is a strange "branch --set-upstream-to" failure for "clones" which > haven't been created using "git clone" but constructed using "git init", "git > remote add" and "git fetch". > > Following script