On Sat, Oct 15, 2016 at 4:06 AM, Martin Langhoff
wrote:
> On Fri, Oct 14, 2016 at 4:58 PM, Kevin Daudt wrote:
>> Correct, this only works when it's unambiguous what branch you actually
>> mean.
>
> That's not surprising, but there isn't a warning. IMHO, finding
> several branch matches is a stron
On Fri, Oct 14, 2016 at 4:58 PM, Kevin Daudt wrote:
> Correct, this only works when it's unambiguous what branch you actually
> mean.
That's not surprising, but there isn't a warning. IMHO, finding
several branch matches is a strong indication that it'll be worth
reporting to the user that the DW
On Fri, Oct 14, 2016 at 04:25:49PM -0400, Martin Langhoff wrote:
> In a (private) repo project I have, I recently tried (and failed) to do:
>
> git checkout v4.1-support
>
> getting a "pathspec did not match any files known to git" error.
>
> There's an origin/v4.1-support, there is no v4.1-su
In a (private) repo project I have, I recently tried (and failed) to do:
git checkout v4.1-support
getting a "pathspec did not match any files known to git" error.
There's an origin/v4.1-support, there is no v4.1-support "local"
branch. Creating the tracking branch explicitly worked.
Other si
4 matches
Mail list logo
