[Pyrex] Source Control System
Gustavo Sverzut Barbieri
barbieri at gmail.com
Sat Oct 13 17:10:57 CEST 2007
On 10/13/07, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> Robert Bradshaw wrote:
> > Greg, correct me if I'm wrong, but I doubt you want the burden of
> > maintaining a central server
>
> That's correct.
>
> > Being able to pass changes back and forth will be mutually
> > beneficial, especially for things like bugfixes.
>
> I think perhaps you're overestimating the amount of automation
> that will be possible in that area. When I incorporate people's
> patches, there's nothing automatic about the process at all.
> I don't really "apply" the patch, I study it to find out
> what's been done, and then re-implement the same ideas --
> often using quite different code. This goes for small things
> like bug fixes as well as larger ones.
Ok, this is your direction, but others (like Cython or people that use
pyrex) would like to apply your changes like that. We're just asking
you to choose a tool that would help us too, maybe it's too much? ;-)
> > For example, with mercurial,
> > type "hg init" and you now have a repository in your working directory
> > (with the history and comments stored in an (invisible) .hg file).
>
> I'm not keen on invisible files, generally. They don't show
> up at all in the Finder, for one thing, so it's easy to forget
> they're there an lose them when dragging stuff from one place
> to another.
>
> Incidentally, one of the things that bothers me about svn is
> the necessity to be scrupulously careful about using the svn
> commands to move and rename files, etc, instead of the normal
> OS ones, which also rules out any use of the Finder for these
> things.
You should _NEVER_ touch these .hg (or .git) directly, and copying
them with Finder will work because you should drag the base folder,
not its contents (makes sense to me).
As for dealing with files moving around, at least GIT does a great job
there, it just works, but I think that HG is also good there, Robert
and others can comment on that.
> > You
> > can back it up by simply dragging the whole folder onto your zip drive
>
> Although if the entire history is kept in the working directory,
> it sounds like the amount to be backed up every day will grow
> larger and larger over time, which doesn't sound so good.
If you change things, these changes need to be stored, so yes, it
grows. But since changes are kept packed, they don't loose too much
space. The whole Linux kernel repository with all its history is not
bigger than 200mb (last kernel's tar.gz is around 50mb).
You can find some numbers http://git.or.cz/gitwiki/GitBenchmarks
(which also shows Hg is not as slow as I thought).
> However, it sounds like mercurial could be interesting, so I'll
> look into it.
Great!
--
Gustavo Sverzut Barbieri
--------------------------------------
Jabber: barbieri at gmail.com
MSN: barbieri at gmail.com
ICQ#: 17249123
Skype: gsbarbieri
Mobile: +55 (81) 9927 0010
More information about the Pyrex
mailing list