A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-September/141655.html below:

[Python-Dev] PEP: Collecting information about git

[Python-Dev] PEP: Collecting information about gitChris Angelico rosuav at gmail.com
Wed Sep 16 02:20:53 CEST 2015
On Wed, Sep 16, 2015 at 5:44 AM, Augie Fackler <raf at durin42.com> wrote:
>> but git is still better at it: ``git add -p``
>> allows me to review and edit patches before commit while ``hg record``
>> commits immediately.
>
> FWIW, I totally *get* wanting a staging area. That said, other than the
> staging area, record (aka commit --interactive) and git add -p are identical
> functionality-wise. We also now ship (at least as of 3.5) a curses UI for
> record, which is quite nice.

Looks like it's time I spun up my own hg, rather than using the 3.1.2
that ships with Debian. A better UI for interactive (partial) commits
would go a long way toward filling the hole left by not having a
staging area; though I'll still miss it, some, in the most complicated
cases (where I use 'git gui' to stage and unstage bits, then check in
'gitk' that it looks right, continue until happy). Fortunately the
complicated cases are rare, but when my non-technical mother or my
technical-but-decades-out-of-date father needs help fixing up a
repository problem, I make good use of git's staging power.

Mentioning in the PEP that some of these things are available as of
version X might help bridge the gap between one author's knowledge and
a core dev's skills.

ChrisA
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4