Re: [PATCH] Documentation/git-add.txt: Explain --patch option in layman terms
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 30, 2009, 23:20 UTC
- Message-ID
- <7vbplw28js.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <87ab1gaol2.fsf@jondo.cante.net>
Jari Aalto <jari.aalto@cante.net> writes:
> Your proposal that starts: > > ...but bypass the initial command menu
No, it doesn't..
Go re-read the message you are responding to, paying extra attention to the parts you snipped from your quote, which was the important part you should have read before you responded.
If you want to start the description with "What it does/what it is used
for", I think it is a good idea. I already made a suggestion for such an
improvement in my message you are responding to.Now, what was that suggestion?
It is in the message your first response was a follow-up to. Again you didn't quote the relevant part in that response, and perhaps that was because you did not even read it before responding.
If you assume that the reader is not familiar with "add -i", then the
above is not descriptive enough, but "Run interactive patch command" is
not an improvement either. We would need a description of "what it is
used for" before "how it would look to you" (i.e.. my rewrite shown
above)."What it is used for" would perhaps read like this.
Review the difference between the index and the work tree, and add
modified contents to the index interactively by choosing which
patch hunks to use.This time I re-quoted things for you because your responses obviously were written without reading or understanding them, but please be careful not to make me do this. I do not have infinite time.