Pranit Bauva <[email protected]> writes: > Hey Jessica, > > You could probably put all the config files in the root repo. Then > make a bash script which can copy them to their respective locations. > Now when you update one script, you can just run that bash script > which will update all the config files. Similarly you can pull the > repo on some other computer and run the bash file there. Hope this > helps!
For a more complicated solution, that doesn't need a bash script, look at the GIT_WORK_TREE environment variable. /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: [email protected] jabber: [email protected] twitter: magthe http://therning.org/magnus Unix is the answer, but only if you phrase the question very carefully. — Unknown -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
