Re: git add -p with new file

From: Duy Nguyen <pclouds@gmail.com>
Date: Dec 7, 2016, 09:22 UTC
Message-ID: <CACsJy8A_YMyEUgX--1tEfJC4aaYfDbFFL8WEs6CHp4a4=mHRjw@mail.gmail.com>
In-Reply-To: <alpine.DEB.2.11.1612062012540.13185@cherryberry.dsgml.com>

On Wed, Dec 7, 2016 at 8:18 AM, Ariel <asgit@dsgml.com> wrote:

Show 8 quoted lines

>
> If you do git add -p new_file it says:
>
> No changes.
>
> Which is a rather confusing message. I would expect it to show me the
> content of the file in patch form, in the normal way that -p works, let me
> edit it, etc.

We could improve it a bit, suggesting the user to do git add -N. But is there a point of using -p on a new file? It will be one big chunk, you can't split anything. Perhaps maybe you want to use 'e' to edit what's added?

> (Note: I am aware I can do -N first, but when I specifically enter the name
> of a new file I feel it should figure out what I mean.)

-- 
Duy