turon / git-rcs-keywords Goto Github PK

Please switch to the mentioned fork to ensure getting the most recent patches and support

The clone will take a huge amount of time in case of big repositories.
Our repository has around 3G and I had to stop the clone after half an hour.

Just to let others know.

Hi, the scripts look promising but I've run into a serious bug:
When switching between branches the filter always inserts the data from the branch I am leaving. Thus the keywords will always show invalid data unless the file with keyword expansion was last edited in the same commit. Which won't be the case in any non-trivial situation. I'm using git 1.7.9 with MinGW. HTH

Regards

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

According to the doc https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#filters_b:

The “clean” filter is run when files are staged.

while the README says:

the clean filter is run on commit.

Smudge filter not working on git pull. When smudge filter runs at that time latest git log is not available. It is updated after smudge filter.

Is there any workaround or is this known limitation of keyword substitution?

Hello,
I don't know, how to ask correctly.
I expand yours code and changed use of keywords

1. $keyword:$ expand to $keyword:value:$
2. $keyword$ replaced with 'value'
3. added version.h example
4. modified s/// to while-cycle (foreach and while)

And I ask you for your opinion

Now is possible to download it from http://nanoware.cz/download/git-rcs.zip . If you are thinking, that is good, I can push it here.

Jindrich

Hi!

I've found #2 filed and closed already, but unfortunately I don't have enough rights to re-open it, so in order to attract your attention I am opening a brand new issue.

Could you please specify license for your project? I personally like MIT for this kind of small things, but what actually matters is to have an explicit statement on how we can use your code.

I am planning to write a blog article about your project and submit a contribution to make it work with git-svn bridge, but I'd like to know what is the license first.

Thanks!

Maybe a license should be added (like the New BSD license)?

Also maybe you could open the wiki, so i could make a page with these thoughts instead of opening an issue about it? :p

The instructions say to specify the hooks in my local $HOME/.gitconfig file. That works fine for just me, but I need my keywords expanded for all Git users, and this includes many who I wouldn't trust to edit a text file.

Since I can hook in an email hook script without requiring any client-side setup whatsoever, I am thinking that there should be a way to configure the git-rcs-keywords hooks by updating files in the hooks directory in the main server repository-- without burdening my users with procedures they are very unlikely to follow successfully.