Re: [PATCH 2/4] commit: introduce a config key to allow as-is commit with i-t-a entries
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Feb 7, 2012, 06:26 UTC
- Message-ID
- <CACsJy8CaFhyzgh6N4ov49Tf0mA8qV5uQESFP2u8U7AduOd59PA@mail.gmail.com>
- In-Reply-To
- <7v1uq741ip.fsf@alter.siamese.dyndns.org>
2012/2/7 Junio C Hamano <gitster@pobox.com>:
Show 11 quoted lines
> Unless you are doing "commit -a" or "commit pathspec", you are responsible > for adding all contents you want to have in the commit before you run the > "git commit" command (and for the purpose of this statement, "add -N" to > tell Git to keey an eye on a path does _not_ add contents). A change to > the file in the working tree that is left unadded is what you decided to > deliberately leave out of the commit, be it a change to a path already in > HEAD, or a path marked with "add -N". Forgetting to add modified file and > forgetting to add a file you earlier used "add -N" amount to the same kind > of risk, and "git status" is the way to make sure your partial commit has > exactly what you want (if you are not worried about partial commit, you > would be doing "commit -a", so the "safety" is a moot point).
We need something in the commit message so that 5 years from now, when someone raises the issue again, (s)he does not have to search the mail archive. May I steal the above paragraph, maybe rephrase a little bit, for commit message?
-- Duy