From: Junio C Hamano <gitster@pobox.com>
To: "Henrik Grubbström (Grubba)" <grubba@grubba.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Patches to avoid reporting conversion changes.
Date: Tue, 01 Jun 2010 21:40:20 -0700 [thread overview]
Message-ID: <7vfx16oxmz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: cover.1275309129.git.grubba@grubba.org
"Henrik Grubbström (Grubba)" <grubba@grubba.org> writes:
> 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 ;-).
next prev parent reply other threads:[~2010-06-02 4:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 14:41 [PATCH v4 0/5] Patches to avoid reporting conversion changes Henrik Grubbström (Grubba)
2010-06-01 14:41 ` [PATCH v4 1/5] sha1_file: Add index_blob() Henrik Grubbström (Grubba)
2010-06-01 14:41 ` [PATCH v4 2/5] strbuf: Add strbuf_add_uint32() Henrik Grubbström (Grubba)
2010-06-01 14:41 ` [PATCH v4 3/5] cache: Keep track of conversion mode changes Henrik Grubbström (Grubba)
2010-06-01 14:41 ` [PATCH v4 4/5] cache: Add index extension "CONV" Henrik Grubbström (Grubba)
2010-06-01 14:41 ` [PATCH v4 5/5] t/t0021: Test that conversion changes are detected Henrik Grubbström (Grubba)
2010-06-02 4:40 ` Junio C Hamano [this message]
2010-06-03 16:00 ` [PATCH v4 0/5] Patches to avoid reporting conversion changes Henrik Grubbström
2010-06-04 0:56 ` Jonathan Nieder
2010-06-04 11:59 ` Henrik Grubbström
2010-06-04 19:42 ` Jonathan Nieder
2010-06-06 10:50 ` Henrik Grubbström
2010-06-07 8:59 ` Finn Arne Gangstad
2010-06-07 16:37 ` Henrik Grubbström
2010-06-07 19:50 ` Finn Arne Gangstad
2010-06-08 15:52 ` Henrik Grubbström
2010-06-09 14:03 ` Finn Arne Gangstad
2010-06-09 18:04 ` Henrik Grubbström
2010-06-10 19:55 ` Finn Arne Gangstad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vfx16oxmz.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=grubba@grubba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).