Re: Memory overrun in http-push.c

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

Re: Memory overrun in http-push.c

From: Matthieu Moy <hidden>
Date: 2016-06-15 22:42:57

Andy Parkins [off-list ref] writes:
On Friday 2007 March 02 14:38, Jakub Narebski wrote:
quoted
First, keyword expansion on checkout (CVS-like) is an abomination;
the proper way is to do it on _build_ time, like git and Linux kernel
What about my SVG example?  There is no build time, the file is the file.
Same with manually written HTML, or even just plain text files, or ...

A typical other example is when you're working with people having some
kind of alergy to revision control systems. Then, you have to send the
source, and they send you back the modified source. That's very hard
to manage without some kind of timestamp within the file.

However, I have to admit that workflows requiring keyword expansions
still appear dirty to me.

A (dirty too) solution is to have a pre-commit hook that would update
the keywords for each modified file. Then, the keyword is in the
source itself.

-- 
Matthieu

Re: Memory overrun in http-push.c

From: Andy Parkins <hidden>
Date: 2016-06-15 22:42:57

On Friday 2007 March 02 15:30, Matthieu Moy wrote:
A (dirty too) solution is to have a pre-commit hook that would update
the keywords for each modified file. Then, the keyword is in the
source itself.
That would be bad for merges though.  I think it's got to be filtered out in a 
pre-commit or equivalent script.


Andy

-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help