Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

[Johannes Schindelin <Johannes.Schindelin@gmx.de>]

Hi Phillip,

On Thu, 8 Nov 2018, Phillip Wood wrote:

> On 07/11/2018 09:41, Junio C Hamano wrote:
> > Here are the topics that have been cooking.  Commits prefixed with
> > '-' are only in 'pu' (proposed updates) while commits prefixed with
> > '+' are in 'next'.  The ones marked with '.' do not appear in any of
> > the integration branches, but I am still holding onto them.
> > 
> > You can find the changes described here in the integration branches
> > of the repositories listed at
> > 
> >      http://git-blame.blogspot.com/p/git-public-repositories.html
> > 
> > --------------------------------------------------
> > 
> > * pw/add-p-select (2018-07-26) 4 commits
> >   - add -p: optimize line selection for short hunks
> >   - add -p: allow line selection to be inverted
> >   - add -p: select modified lines correctly
> >   - add -p: select individual hunk lines
> > 
> >   "git add -p" interactive interface learned to let users choose
> >   individual added/removed lines to be used in the operation, instead
> >   of accepting or rejecting a whole hunk.
> > 
> >   Will discard.
> >   No further feedbacks on the topic for quite some time.
> 
> Unfortunately I've not found time to work on this recently and don't see
> myself doing so before the new year so I think it makes sense to drop it.
> Hopefully I can come up with something next year, it would be nice for users
> to avoid having to edit patches where possible.

If I understand correctly, this patch series essentially imitates on the
console what you can do in Git GUI by selecting multiple lines in the diff
and then "Stage Selected Lines"?

If my understanding is correct, then yes, I would be very much in favor of
having this feature, too.

Thanks,
Dscho