Mike wrote:
Linus Torvalds wrote:
Some people don't split this up, and they tend to make horrible
horrible mistakes, like checking in the *results* of the
post-processing too (ie binary result blobs that can be regenerated
from the other files), because they don't make a clear separation
between the parts they do development on, and the end result.
Honestly, I think your mode of thinking is centered around compiled
languages and linux app(/kernel) development. The web app
development/deployment model is very different.
With PHP, Python, and Ruby, the development is the deployment. The
source is the output. You can't develop web apps in those languages
unless the source files you're working on are under the doc root of your
development server. "the parts they do development on" and "the end
result" *are* the same files.
Not for me. I've always had my source separate from development docroot
even before I was using proper SCM's. I've written stuff in all three
languages you mention where deployment to the docroot (development or not)
was more than a simple copy.
-
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
