[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190822010203.GG22020@lenoir>
Date: Thu, 22 Aug 2019 03:02:04 +0200
From: Frederic Weisbecker <frederic@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Oleg Nesterov <oleg@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
John Stultz <john.stultz@...aro.org>,
Anna-Maria Behnsen <anna-maria@...utronix.de>
Subject: Re: [patch V2 00/38] posix-cpu-timers: Cleanup and consolidation
On Thu, Aug 22, 2019 at 02:54:34AM +0200, Christoph Hellwig wrote:
> > The series applies on top of:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
> >
> > and is available from git as well:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.timers/core
>
> Btw, for some reason git here seems to be very unhappy about that remote:
>
> Fetching tip
> error: cannot lock ref 'refs/remotes/tip/WIP.timers/core': 'refs/remotes/tip/WIP.timers' exists; cannot create 'refs/remotes/tip/WIP.timers/core'
> From https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> ! [new branch] WIP.timers/core -> tip/WIP.timers/core (unable to update local ref)
> error: Could not fetch tip
>
> which repeats every time I fetch. I can't of anythign particular on
> my side that would cause this.
Yeah I had to run "git remote prune tip" and fetch again.
Apparently there was an old remote branch tip/WIP.timers and git
seem to refuse to have a new subpath branch.
Powered by blists - more mailing lists