On Mon, Mar 26, 2012 at 10:06:20AM -0000, Joseph Wakeling wrote:
> Have to say that for me at least, "last committed revision" is to me a lot more comprehensible than "working tree basis revision". What's the reason for distinguishing them? "Base revision of the current working tree" may be a more accurate description, but it may be more confusing than it's worth to users.
They *can* be different in some situations.
If I push to a remote branch with a working tree over e.g. sftp, that will only update the branch and leave the working tree alone. This is because working trees can't be accessed over sftp, only locally. In other words, the branch last revision has been changed but the working tree basis revision hasn't.
On Mon, Mar 26, 2012 at 10:06:20AM -0000, Joseph Wakeling wrote:
> Have to say that for me at least, "last committed revision" is to me a lot more comprehensible than "working tree basis revision". What's the reason for distinguishing them? "Base revision of the current working tree" may be a more accurate description, but it may be more confusing than it's worth to users.
They *can* be different in some situations.
If I push to a remote branch with a working tree over e.g. sftp, that will only update the branch and leave the working tree alone. This is because working trees can't be accessed over sftp, only locally. In other words, the branch last revision has been changed but the working tree basis revision hasn't.
Cheers,
Jelmer