All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Francis Galiegue <fg@one2team.com>
Cc: Michal Nazarewicz <mina86@tlen.pl>, git@vger.kernel.org
Subject: Re: Something like $Id$, $Revision$ or $Date$?
Date: Mon, 10 Nov 2008 21:32:03 +0100	[thread overview]
Message-ID: <200811102132.05472.jnareb@gmail.com> (raw)
In-Reply-To: <200811102124.59973.fg@one2team.com>

Dnia poniedziałek 10. listopada 2008 21:24, Francis Galiegue napisał:
> Le Monday 10 November 2008 21:17:29 Jakub Narebski, vous avez écrit :

> > Well, _some_ command has to be invoked to expand keywords. "git add"
> > doesn't do that (perhaps it should?), so you need to use checkout.
> >
> 
> If "git add" aims to do that, you'd have to be very, VERY careful, not to 
> substitute in the wrong place to start with, not to attempt substitution in 
> binary files...
> 
> And this would have a sizeable cost, imho. If you really want to do this, 
> isn't there a hook somewhere that can do that for you, instead of modifying 
> git add directly?

If I remember correctly there was idea to add 'pre-add' or 'post-add'
hook...

-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-11-10 20:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  0:22 Something like $Id$, $Revision$ or $Date$? Michal Nazarewicz
2008-11-10  0:43 ` Sverre Rabbelier
2008-11-10  1:16   ` Michal Nazarewicz
2008-11-10  3:43     ` dhruva
2008-11-10  9:49       ` Michal Nazarewicz
2008-11-10  7:26     ` Johannes Sixt
2008-11-10 12:25     ` Johannes Schindelin
2008-11-10 14:05       ` dhruva
2008-11-10 15:48       ` Michal Nazarewicz
2008-11-10 15:58         ` Francis Galiegue
2008-11-10 15:59 ` Jakub Narebski
2008-11-10 17:38   ` Michal Nazarewicz
2008-11-10 18:03     ` Jakub Narebski
2008-11-10 20:00       ` Michal Nazarewicz
2008-11-10 20:17         ` Jakub Narebski
2008-11-10 20:24           ` Francis Galiegue
2008-11-10 20:32             ` Jakub Narebski [this message]
2008-11-10 20:58               ` Brian Gernhardt

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=200811102132.05472.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=fg@one2team.com \
    --cc=git@vger.kernel.org \
    --cc=mina86@tlen.pl \
    /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.