From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Johannes Sixt <j.sixt@viscovery.net>, "Mestnik\,
Michael J - Eagan\,
MN - Contractor" <Michael.J.Mestnik@usps.gov>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Using Format/export-subst Howto.
Date: Mon, 17 Sep 2012 13:21:28 -0700 [thread overview]
Message-ID: <7v4nmwv1rr.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <505722DD.3000806@drmicha.warpmail.net> (Michael J. Gruber's message of "Mon, 17 Sep 2012 15:17:17 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Junio C Hamano venit, vidit, dixit 15.09.2012 00:26:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> Michael J Gruber <git@drmicha.warpmail.net> writes:
>>>
>>>> you need to "rm file && git checkout file"). If the user has to
>>>> update $Id$ to match the current sha1 (by remembering to do a
>>>> more forceful checkout than checkout -f) then one half of that
>>>> feature is useless.
>>>
>>> As if there is any value in "$Id$" _feature_. It's a checkbox
>>> item, nothing more ;-).
>>
>> Having said that, I think you could do something along this line (I
>> am thinking aloud, so there may be leaps in the logic below).
>> ...
>
> You've convinced me not to try this in-core...
Quite contrary, I think the approach outlined is a reasonable way
forward. I do not care about a checkbox feature like $Id$ that is
incomatible with the fundamental concept in Git, but the approach
would help people who started their history with wrong CRLF
settings, tweak the attributes and then scratch their head trying to
repeatedly run "checkout", "reset --hard", etc. and still never
seeing the right thing to happen.
next prev parent reply other threads:[~2012-09-17 20:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 12:20 Using Format/export-subst Howto Mestnik, Michael J - Eagan, MN - Contractor
2012-09-14 13:03 ` Michael J Gruber
2012-09-14 15:06 ` Johannes Sixt
2012-09-14 15:27 ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-14 15:39 ` Johannes Sixt
2012-09-14 16:05 ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-14 21:09 ` Michael J Gruber
2012-09-14 21:23 ` Junio C Hamano
2012-09-14 22:26 ` Junio C Hamano
2012-09-17 13:17 ` Michael J Gruber
2012-09-17 13:26 ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-17 20:21 ` Junio C Hamano [this message]
2012-09-18 8:24 ` Michael J Gruber
2012-09-17 12:12 ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-17 13:45 ` Michael J Gruber
2012-09-17 14:08 ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-17 14:21 ` Michael J Gruber
2012-09-17 15:52 ` Mestnik, Michael J - Eagan, MN - Contractor
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=7v4nmwv1rr.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Michael.J.Mestnik@usps.gov \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).