Dear Juno
Thanks for your answer.
My fair criticism in my previous emails (and below) is just to try to convince
you that with a few short sentences you risk to transmit only vague ideas,
while a serious user is interested to understand the behavior of git in any
occurrence, with no
Dear Junio,
thanks for your answer and you availability to revise the man text. Below my
(irreverent) comments
On Thursday 19 September 2013 10:43:16 Junio C Hamano wrote:
Let's see how we can improve the text. Points to notice are:
* by updating the index and the files does not say how
r.duc...@gmail.com writes:
mmm maybe I'm wrong, but it seems to me that the first statement
on the index (above) is oversimplifing.
Yes, it was simplified to illustrate the principle, not even trying
to be exhaustive.
The principle is that we allow you to check out a different branch
when you
Dear all
I'm not a power git user but I profit of git every day and I like to fully
understand what I do.
The man section for git checkout is too vague for my taste. In particular it is
not clearly (unambiguously) stated what happens to index and worktree whenever
local uncommitted changes
r.duc...@gmail.com writes:
The man section for git checkout ... In
particular it is not clearly (unambiguously) stated what happens
to index and worktree whenever local uncommitted changes are
around.
In the current text, the key information is in two places:
'git checkout' branch::
5 matches
Mail list logo
