| 1 |
On Thu, Mar 26, 2009 at 11:59 AM, Jonas Bernoulli <jonas@×××××××.li> wrote: |
| 2 |
> That is obviously not what you mean but how I understand it. So please |
| 3 |
> tell me, in a bit more detail. |
| 4 |
|
| 5 |
wow, that explanation makes little sense to me |
| 6 |
|
| 7 |
this is how it should work |
| 8 |
|
| 9 |
repo config.git with branches master host1 host2 host3 etc |
| 10 |
|
| 11 |
it could work like the following |
| 12 |
|
| 13 |
apache.git with branches master host1 host2 host3 |
| 14 |
postfix.git with branchnes master host1 host2... |
| 15 |
bind.git with branches... |
| 16 |
|
| 17 |
I think what you've proposed is |
| 18 |
repo config.git with branches apache postfix bind |
| 19 |
|
| 20 |
this doesn't work, why? you can't merge branches, branches are mostly |
| 21 |
supposed to have similar content and be merge-able, they aren't |
| 22 |
supposed to contain completely separate data, use different repo's for |
| 23 |
that. I don't consider the whole of config separate myself, like I |
| 24 |
said, I think they are related by host, or even by type of box, one |
| 25 |
could also define |
| 26 |
|
| 27 |
repo config.git with branches master desktop, server, router, database |
| 28 |
server, web server, mail server, dns server, etc. |
| 29 |
|
| 30 |
in fact the system should create config.git master should be stored |
| 31 |
all the default configs, it should auto-detect the host.domain.tld and |
| 32 |
create a branch with that name, and after that merge master into that |
| 33 |
branch... or whatever branch the admin sets as default for the host. |
| 34 |
-- |
| 35 |
Caleb Cushing |
| 36 |
|
| 37 |
http://xenoterracide.blogspot.com |
Archives