On Tuesday, 25 June 2013 at 06:46:28 UTC, Jonathan M Davis wrote:
On Tuesday, June 25, 2013 08:38:01 Marco Leise wrote:
Am Mon, 24 Jun 2013 08:45:26 -0700
schrieb Andrei Alexandrescu <[email protected]>:
> http://stackoverflow.com/questions/17263604/i-have-a-c-repository-but-gith
> ub-says-its-d
>
> Andrei
This is why you don't put automatically generated files in
version control ... Especially when they have the file ending
used by an indexed PL on GitHub ;)
Yeah. That was the great faux pas of that question. I'm not
aware of any good
reason to put generated files in version control unless they
were only
generated once and will never be generated again.
- Jonathan M Davis
Well, depends how you use the version control I guess. You *can*
use it for more than just going back in time or concurrent edits:
You can use it as a redistributable network folder.
The company I work for does it that way. It means when you
checkout a project, you don't have to run 10+ different tools to
generate whatever it needs to generate: You are ready to roll.
You save on time and headaches. Whenever someone changes the xml,
you don't have to regenerate everything every time you resync.
The overall time and overhead wasted by a few guys checking in
their generated files is more than made up for everyone else not
having to worry (or even know) about it. But to each their own of
course, this works for _us_ .
Also, it means you can look at the generated files inside the
repository.
