Re: What's cooking in git.git (Aug 2015, #05; Fri, 28)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> * dt/refs-bisection (2015-08-28) 5 commits
>  - bisect: make bisection refs per-worktree
>  - refs: make refs/worktree/* per-worktree
>  - SQUASH???
>  - path: optimize common dir checking
>  - refs: clean up common_list
>
>  Move the refs used during a "git bisect" session to per-worktree
>  hierarchy refs/worktree/* so that independent bisect sessions can
>  be done in different worktrees.
>
>  Will merge to 'next' after squashing the update in.

Sorry if I am missing something or repeating what myself or someone
else like Michael already said, but in the current doc there is:

       Eventually there will be no more revisions left to bisect, and
you will have been left with the first bad kernel revision in
       "refs/bisect/bad".

If we now just use "refs/worktree/bisect/bad" instead of
"refs/bisect/bad", it might break scripts that rely using
"refs/bisect/bad".
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]