Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Your suggestion good work if “Filling.txt” be kind of configuration file. And smudge script copy from (FillingB.txt, FillingC.txt) to Filling.txt. But in my project the file “Filling.txt” is a source file, which often edited and must save history on each branch. Commented Dec 22, 2013 at 9:12
  • @Jarikus simply make sure your file include templates like @val1@, @val2@, ..., that the smudge script can easily replace. And add a clean script which will update that same file automatically on commit, with any modification you have done to that source file. Like the smudge script,you declare the clean script in a .gitattributes file. Commented Dec 22, 2013 at 9:51
  • Templates not convenient to my instance, because file ‘Filling.txt’ too different on each version. I`am make scheme, for more approach to my problem: i.sstatic.net/pDb0D.png Commented Dec 22, 2013 at 10:04