On 2015-09-18, John Wong wrote:
> if you are okay with cloning a huge repository then I don't see a problem.
Ah yes, if the repository got cloned a lot that would be a problem.
The repository in question doesn't get cloned (it does get backed up).
As I mentioned, it's subversion. Subversion is
On Fri, Sep 18, 2015 at 2:50 AM, Peter Otten <__pete...@web.de> wrote:
> Ben Finney wrote:
>
> > David Aldrich writes:
> >
> >> I have setup Sphinx for my Python project. We keep all our code and
> >> documentation in Subversion.
> >
> > It's a good idea to keep *source* files in VCS.
> >
> > The
Ben Finney wrote:
> David Aldrich writes:
>
>> I have setup Sphinx for my Python project. We keep all our code and
>> documentation in Subversion.
>
> It's a good idea to keep *source* files in VCS.
>
> It's a bad idea to keep automatically-generated files in VCS; it's
> especially bad to do s
On Fri, Sep 18, 2015 at 9:37 AM, Ben Finney wrote:
> David Aldrich writes:
>
>> I have setup Sphinx for my Python project. We keep all our code and
>> documentation in Subversion.
>
> It's a good idea to keep *source* files in VCS.
>
> It's a bad idea to keep automatically-generated files in VCS;
On 2015-09-17, Ben Finney wrote:
> The VCS should track only those files that humans edit directly.
While I agree that files automatically generated shouldn't be checked
in to a VCS, I'm in favor of putting key binary files under VCS if
they are required to do the build. We often check deveopme
David Aldrich writes:
> I have setup Sphinx for my Python project. We keep all our code and
> documentation in Subversion.
It's a good idea to keep *source* files in VCS.
It's a bad idea to keep automatically-generated files in VCS; it's
especially bad to do so if they need to be generated agai
