Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working currently? #10

Open
dylandog opened this issue Mar 8, 2012 · 10 comments
Open

Not working currently? #10

dylandog opened this issue Mar 8, 2012 · 10 comments

Comments

@dylandog
Copy link

dylandog commented Mar 8, 2012

Unless i rm and checkout again manually every single file, it doesn't seem to work? is it supposed to?

@kabel
Copy link

kabel commented Mar 9, 2012

That's right. Smudge is only run on checkout. If you are checking out for the first time (or from another branch) the correct git information is not available. After the initial checkout/switch you can run git checkout HEAD to "refresh" things.

@kimmormh
Copy link

kimmormh commented Mar 9, 2012

There's now an installer script to work around this in most cases

@kimmormh
Copy link

kimmormh commented Mar 9, 2012

Hint: pls see my fork

@dylandog
Copy link
Author

dylandog commented Mar 9, 2012

@kimmormh your install script gives errors on osx

$ ./install.sh 
./install.sh: line 20: syntax error near unexpected token `else'
./install.sh: line 20: `    else'
$

@kabel so everytime i commit anything, i need to checkout the whole project? That's less than ideal. I noticed that my original issue wasn't stating alot, but it was meant "after commit & push, unless i rm and checkout the file again it doesn't work"

@kabel
Copy link

kabel commented Mar 10, 2012

There's no need to rm. Just doing a checkout (which only takes a second), triggers the filters to run again.

I understand that it's less than ideal, but that's how git works (for smudge/clean filters). You could certainly "automate" this process with git hooks like post-commit or post-receive (for remote). In fact, I use a post-receive hook on my production remote to do just that.

@kimmormh
Copy link

Sorry bout the syntax error guys, it's fixed now

@kimmormh
Copy link

On Fri, 2012-03-09 at 15:39 -0800, dylandog wrote:

It's fixed now

@kimmormh your install script gives errors on osx

$ ./install.sh 
./install.sh: line 20: syntax error near unexpected token `else'
./install.sh: line 20: `    else'
$

@kabel so everytime i commit anything, i need to checkout the whole project? That's less than ideal. I noticed that my original issue wasn't stating alot, but it was meant "after commit & push, unless i rm and checkout the file again it doesn't work"


Reply to this email directly or view it on GitHub:
#10 (comment)

@dylandog
Copy link
Author

@kimmormh confirmed!
@kabel would you be so kind to tell me how to use post-commit post-receive to populate the rcs tags automatically? :)

@kabel
Copy link

kabel commented Mar 12, 2012

You can install a git hook by installing a file like https://gist.github.com/2024831 in the $GIT_DIR/hooks/ with the name of the hook you'd like to attach it to (do forget to chmod a+x file).

For more information about how to install git hooks, please see http://schacon.github.com/git/githooks.html

@kenorb
Copy link

kenorb commented Jun 20, 2013

Doesn't work for me either.
On Mac:
git version 1.8.2.1 (Mac), perl v5.12.4) built for darwin-thread-multi-2level
Also on Ubuntu:
git version 1.7.9.5, perl v5.14.2) built for x86_64-linux-gnu-thread-multi

Cloned the repo, did: git checkout HEAD
and still nothing in hello.c

Any clue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants