My immediate thoughts are that you are looking for more of a template
system, where you have some set of base-templates, and each customer has
some custom-templates that extend and/or override the base ones.
I don't think you should base the templating mechanism itself on Git.
However, once you have a working template engine, there's nothing wrong
with keeping the source code (the templates) in a Git repository.
On Tuesday, July 10, 2012 2:38:45 PM UTC+2, jay_m wrote:
> I support a software package that distrubutes small customizable code
> files, we call them posts. These code files are a small script based on
> our proprietary programming language, something similar to BASIC. Each of
> our customers will have one or more posts. Most post files will be nearly
> identical, however there will be some modifications that need to be made
> for each customer. We will also heavily modify certain posts for specific
> customer needs.
> So what I am looking for is a set number of "default" posts, that I can
> customize and configure for each customer. I would like to be able to go
> back to my defaults and make changes, updates and improvements and have
> those changes propagate to each of my customers posts that are based on
> that default.
> Currently I mostly handle this by hand but am looking for a better way. I
> have used other projects that use GIT, though I have never been a
> contributor (my programming skills are limited). Is this a proper use of
> GIT? Is there a better tool that you are familiar with? If GIT is right,
> where is my beginning point?
> Thanks for your opinions and input.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at