At Wed, 29 Dec 2010 22:11:39 +0100,
Moritz Bunkus wrote:
>
> Hey,
>
> On Wed, 29 Dec 2010 12:05:45 -0900, Dave Abrahams <[email protected]>
> wrote:
>
> > `k' doesn't make sense to me, intuitively, for the operation you're
> > describing; I'd expect it to leave the history intact except for that
> > one commit, i.e. rebase all its children on its parent.
>
> Alright, and what about making 'X' context dependent instead?
Let me see if I understand that scenario:
`x' on a commit resets to that commit but leaves the working tree
`X' not on a commit discards the working tree
`X' on a commit discards the working tree and resets to that
commit (i.e. --hard)
Makes perfect sense to me. I guess the obvious question is:
`x' not on a commit does ????
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
