Hi, On Wed, 11 Feb 2009, Ciprian Dorin, Craciun wrote: > By moving the repository I mean moving it on another machine... > Let me give you an example... > > Thus (inspired by one of my current usages of Git) suppose I'm > working at a scientific project (let's assume algorithmic nature) and > after I succeed in having a working version of my algorithm, I decide > to test it on a better hardware with bigger workloads... Already you showed that your workflow leaves to be desired. You need to move the repository using filesystem commands now. Why? Because you have stuff in .git/ that does not belong there, and does not get pushed or fetched as a consequence. In similar cases, I followed three different options (and yes, I use all of them, in different repositories): - commit the scripts (that works amazingly well with Git :-) - have an independent branch for the scripts that I check out in a subdirectory, or - put the scripts into a submodule right away, when they are useful for more than one project. Hth, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
