git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Integrating with hooks
Date: Thu, 15 Nov 2007 02:43:22 +0100	[thread overview]
Message-ID: <fhg87q$k21$1@ger.gmane.org> (raw)
In-Reply-To: 20071115011837.GD32746@penguin.codegnome.org

Todd A. Jacobs wrote:

> On Wed, Nov 14, 2007 at 12:07:29AM +0100, Jakub Narebski wrote:
> 
>> Take a look at gitattributes(5), namely 'filter' attribute.
> 
> Thanks, I took a look at the man page you suggested. The "ident" feature
> almost does what I want, but doesn't seem to take any sort of format
> string. 

The `ident` feature provides only sensible Id for a file (if you want to
avoid potentially rewriting _all_ and not only changed files on checkout /
switching branch / reset --hard). All Ids which have commit info, like
commit id, commit date, author are not sensible in mentioned sense.

> So, I thought I'd explore "filter," but can't really find any 
> examples of how to implement the smudge and clean commands, which seem
> to be what I'm really trying to do here.
> 
> Is there an example somewhere that you can point me to? The man page
> doesn't really show any examples of how to implement the filter
> attribute, so I'm a little unsure how to proceed.

Cannot help you there, but see examples of `diff` and `merge` attributes,
it should I think be similar.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-11-15  1:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 17:37 Integrating with hooks Todd A. Jacobs
2007-11-13 23:07 ` Jakub Narebski
2007-11-15  1:18   ` Todd A. Jacobs
2007-11-15  1:43     ` Jakub Narebski [this message]
2007-11-15  1:43     ` Johannes Schindelin
2007-11-15  7:57     ` Johannes Sixt

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='fhg87q$k21$1@ger.gmane.org' \
    --to=jnareb@gmail.com \
    --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 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).