Question about Source Control
frank at chagford.com
Fri Mar 21 06:40:42 CET 2014
"Cameron Simpson" <cs at zip.com.au> wrote in message
news:20140321013313.GA58343 at cskk.homeip.net...
> Someone intending to clone the project and develop will probably
> want the whole repository; as Gregory says - they can then easily
> push/pull with others.
> For Frank, the size of the repo is not the size of the bare code *
> number of changesets. There are many diff-level steps in there,
> making for a much smaller size. And code is small; really really
Ok, I think I've got it.
To make the software available to anyone who just wants to run a stable
version, copy the working directory of the 'major release' repository to a
directory of its own, without the .hg stuff, and make it available for
For everyone else, just make the full repository available, and don't worry
about the size.
'Everyone else' would include those wishing to collaborate on the project,
and those who just wish to keep up to date with the latest updates.
Actually my concern was not the 'size' of the full repository, but the
prospect of wading through thousands of changesets most of which are ancient
history. However, I assume that the experienced user will adopt habits such
as 'hg log tip:-10' to review the last 10 changesets, so it should not be a
More information about the Python-list