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 --set-upstream-to" failure for "clones" which haven't been
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" which
>>> haven't been created using "git clone" but
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 add" and "git fetch".
Foll
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 first creates a "main" repo
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 o
5 matches
Mail list logo