Re: Using Format/export-subst Howto.

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: Using Format/export-subst Howto.

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:54:47

Michael J Gruber [off-list ref] writes:
Junio C Hamano venit, vidit, dixit 15.09.2012 00:26:
quoted
Junio C Hamano [off-list ref] writes:
quoted
Michael J Gruber [off-list ref] writes:
quoted
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.

Re: Using Format/export-subst Howto.

From: Michael J Gruber <hidden>
Date: 2016-06-15 22:54:47

Junio C Hamano venit, vidit, dixit 17.09.2012 22:21:
Michael J Gruber [off-list ref] writes:
quoted
Junio C Hamano venit, vidit, dixit 15.09.2012 00:26:
quoted
Junio C Hamano [off-list ref] writes:
quoted
Michael J Gruber [off-list ref] writes:
quoted
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.
Maybe I should have said "...not to try this myself..." to make it
clearer: The approach you outlined sounds not only reasonable but the
perfect solution to this and other problems. But it's over my head and
time limit (and it's not my itch either). It touches the inner core
(index format and handling) and needs to be done diligently, too much
for a quick patch on the side of my $DAYJOB. (Though, thinking about it:
some colleagues use a similar hg feature to revision stamp their LaTeX
preprints, and working Id could help win them over.)

Michael
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help