Re: [PATCH v4 0/5] Patches to avoid reporting conversion changes.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 2, 2010, 04:40 UTC
- Message-ID
- <7vfx16oxmz.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <cover.1275309129.git.grubba@grubba.org>
"Henrik Grubbström (Grubba)" <grubba@grubba.org> writes:
Show 5 quoted lines
> This is useful for repositorys not containing fully normalized files > (eg containing CRLF's or expanded $Id$ strings), where a later attribute > change implies a conversion mode change. Without this set of patches > the user would need to recommit semantically unchanged files to get > a clean index.
A more fundamental (or perhaps "silly") question is if that "user would need to" is necessarily a bad thing. If the user wants to cleanse such abnormality in the recorded blobs, shouldn't there be a conscious act, iow, a commit that records that "I am fixing that mistake, and from now on, the recorded data are normalized"?
Perhaps I am missing something very trivial that you have already explained to the list but I forgot amid my moving and other confusion, and if that is the case I apologize in advance ;-).