Re: Git question: when using branches, how does git treat working files when changing branches?

[Michael Heerdegen]

Alan Mackenzie <address@hidden> writes:

> Sometime, maybe.

I too think it's worth the time (now).

> Trouble is, it's all more stuff to learn, and it might not work well
> for me.

But maybe it would work very well for you.

In the case of git, you have huge man pages that explain tons of options
using terms that are defined nowhere; any command can do a variety of
quite different things that one can hardly remember.

With Magit, you don't need to remember git command options.  You don't
even have to remember lots of magit command names and key bindings,
because most stuff is called via self-explanatory popups.

So you would probably save much time in the midterm.  Once you have used
the (interactive) log where you can just hit RET on a commit and see the
diff and the commit message, or used Ediff to stash, you'll never want
to miss that.

In the case of stashing: Just hit z z RET and you have a stash
named "on [branch] [commit]" whose origin is obvious.

Mmh, it's 1:28 now...


Regards,

Michael.