[Python-Dev] Branching without losing your build products [was: We should be using a tool for code reviews]

[Barry Warsaw]

On Oct 01, 2010, at 01:09 PM, Stephen J. Turnbull wrote:

>Barry Warsaw writes:
>
> > I should note that I don't particularly like colocated/named
> > branches.  I personally much prefer separate directories for each
> > feature or bug I'm working on.  It helps me keep track of what I'm
> > doing.  I have a fast machine so recompiling all of Python is no
> > big deal.
>
>Note that once you have a branch with all of Python built, for any of
>hg, git, bzr you may prefer to clone the branch/repo with "cp -r" or
>"rsync" rather than "$VCS clone".  The reason for doing it with "$VCS
>clone" is to get a pristine workspace without any cruft like editor
>backups or build products.  If you *want* a crufty workspace (and in
>this case some people do), a recursive copy is a better tool.

Yep, absolutely agree.  I also use 'cp -a' or 'rsync -avz' when I want that
crufty workspace transfered to another (local) machine.

In general though, when I'm working on feature or bug branches, I want a
pristine working directory.

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20101001/4730a99d/attachment.pgp>