committing some lines

[Alessandro Dentella]

>
> Mercurial doesn't have a staging area / index / cache, and I don't miss it.
>>
>> I miss it a lot, since it makes it much harder to split the current state
>> of the working directory into smaller pieces.
>>
>> Maybe a top-level commit which get amended (as you mention in your other
>> post) can work like a staging area. Actually I don't care about how this is
>> solved, as long a tooling is powerful — and this is what mercurial is
>> lacking,
>>
>> "hg commit --interactive" works per-chunk only — which is not
>> fine-grained enough for my needs. And the ncurses interface available for
>> "hg commit --interactive" is, well, has potential for improvement.
>>
> Heh. I guess this is where we diverge. I love the ncurses interface of `hg
> commit -i`, and it is plenty capable of sub-chunk (line) operation. I'm not
> familiar with the non-ncurses interface, since when I accidentally end up
> in it, I feel like I'm in some 90s throwback interface and exit immediately.
>

I do live `hg commit -i` that totally resets the advantage of a staging
area.
More than this, I can't understand how git guys can be happy with the
staging area for one reason: all tools (tests, development servers, compile
tools) only see the working directory, so it's much more meaningful to
start from the working dir and not from index to commit...

sandro
*:-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20231002/7a612177/attachment.html>