All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: git@vger.kernel.org
Subject: Re: Memory overrun in http-push.c
Date: Fri, 02 Mar 2007 16:30:11 +0100	[thread overview]
Message-ID: <vpqd53racjg.fsf@olympe.imag.fr> (raw)
In-Reply-To: <200703021523.37010.andyparkins@gmail.com> (Andy Parkins's message of "Fri\, 2 Mar 2007 15\:23\:35 +0000")

Andy Parkins <andyparkins@gmail.com> writes:

> On Friday 2007 March 02 14:38, Jakub Narebski wrote:
>
>> 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

  reply	other threads:[~2007-03-02 15:30 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 15:15 Memory overrun in http-push.c Eygene Ryabinkin
2007-02-28 15:41 ` Andy Parkins
2007-02-28 15:42   ` Johannes Schindelin
2007-03-01  5:13   ` Eygene Ryabinkin
2007-03-01  8:15     ` Alex Riesen
2007-03-01  9:11       ` Eygene Ryabinkin
2007-03-01  9:21         ` Alex Riesen
2007-03-01 11:26           ` Eygene Ryabinkin
2007-03-01  9:32       ` Junio C Hamano
2007-03-01 10:04         ` Alex Riesen
2007-03-01 10:40         ` Andy Parkins
2007-03-01 12:00         ` Eygene Ryabinkin
2007-03-01 12:08           ` Junio C Hamano
2007-03-01 13:20             ` Eygene Ryabinkin
2007-03-01 17:11           ` Johannes Schindelin
2007-03-01 18:31             ` Andy Parkins
2007-03-01 18:41               ` Johannes Schindelin
2007-03-01 19:31                 ` Andy Parkins
2007-03-01 20:43                   ` Johannes Schindelin
2007-03-02 10:05                     ` Andy Parkins
2007-03-02 14:46                       ` Jakub Narebski
2007-03-02 15:22                         ` Andy Parkins
2007-03-02 19:16                       ` Johannes Schindelin
2007-03-02 19:42                         ` Andy Parkins
2007-03-04  8:17                       ` Daniel Barkalow
2007-03-04  8:31                         ` Junio C Hamano
2007-03-04  9:18                           ` Daniel Barkalow
2007-03-01 21:43             ` Alex Riesen
2007-03-01 21:54               ` Shawn O. Pearce
2007-03-01 17:52           ` Uwe Kleine-König
2007-03-02 14:38           ` Jakub Narebski
2007-03-02 15:17             ` Johannes Schindelin
2007-03-02 22:52               ` identifying blobs (was Re: Memory overrun in http-push.c) Junio C Hamano
2007-03-02 23:10                 ` Linus Torvalds
2007-03-02 15:23             ` Memory overrun in http-push.c Andy Parkins
2007-03-02 15:30               ` Matthieu Moy [this message]
2007-03-02 15:48                 ` Andy Parkins
2007-02-28 16:36 ` Florian Weimer
2007-03-01  5:19   ` Eygene Ryabinkin

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=vpqd53racjg.fsf@olympe.imag.fr \
    --to=matthieu.moy@imag.fr \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.