On Jan 17, 2008 2:15 AM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > > - Most sane people want to deploy and test separately. In particular, you > want to test *before* you deploy. People make mistakes, they don't want > to show them. Or there are consistency requirements, and/or you simply > want to deploy to multiple sites simultaneously. All of which really > re-inforces the "develop separately" mentality, where the actual > deployment is then a separate "now I'm ready, let's push out the > result". > Using git to manage deployment environment and even as deployment tools is not always a bad idea. 1. In case where development and deployment environment are almost the same, such as html files, js files, binding the two environments as one is convenient. 2. Event In the case where the two environement are different very much, managing deployment environment in git sometimes still seems good, since we can easily back to any earlier version or fix some urgent bug ASAP (surely for the non-generated files). 3. Use 'git pull' as deploy command seems simple enough. > > Linus > > > > - > 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 > -- Ping Yin - 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
