Hi, I've been tracking Junio's git repository for a year or two and I've used git-bisect many times, but yesterday I got very disoriented while using git-bisect and git-branch together. I think I was confused by the output of 'git-branch -v'. As an example of the new behavior of git-branch, here is what I see this morning after pulling from Linus: $git-branch -v * master ae9458d Merge git://git.infradead.org/battery-2.6 origin 8af03e7 Merge branch 'for-2.6.25' of git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc (I discovered the -a flag just this morning.) $git-branch -av * master ae9458d Merge git://git.infradead.org/battery-2.6 origin 8af03e7 Merge branch 'for-2.6.25' of git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc origin/master aa62999 x86: fix bootup crash in native_read_tsc() In my confusion yesterday, I think I created a new 'origin' which has nothing to do with Linus' repository -- but I'm not sure. The old behavior of 'git-branch' always listed 'origin' as well as 'master', but (I think?) that 'origin' is no longer displayed using just -v. Is this correct? If so, what would be the right way to un-bollocks my local repository? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| H. Peter Anvin | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Eric W. Biederman | Remaining straight forward kthread API conversions... |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
git: | |
