Tags & production questions

[Mark A. Flacy]

On 2007.05.03 11:29, Guido Ostkamp wrote:
> Hello Mark,
> 
>> What I would do is...
>> 
>> When you release a version, you should clone the repository into  
>> abugfix repository.  Your bug fixes are developed in *that* repo, not  
>> the current development stream.  You can pull the fixes from the  
>> bugfix repo into the current one.
> 
> well, in my case the fix has already been developed. Of course, it  
> could be backported into a cloned repository, but having seperate  
> repositories for each version means that you don't have the complete  
> history in one repository so that tools showing the different branches  
> don't work any longer, correct?

No.

Your current development stream will still have *all* the history in it,  
minus the changes made in the cloned branch (i.e. the clone made at  
release time) until you merge them across.

Your cloned stream will have all the history that was available when it  
was cloned.

The least error prone method of branching in Mercurial (IMO) is via  
cloned repositories.

> 
> Furthermore I think you need significantly more disk space if each  
> developer would have to keep several cloned repositories in his home  
> directory.

If you are developing under Windows, maybe.  Linux/Unix will hard link  
on cloning if possible. See  
http://www.selenic.com/mercurial/wiki/index.cgi/WindowsInstall?highlight=%28cloning%29%7C%28hardlink%29#head-fdd32e8f8fd45ec6231a3bccb94cc6a66c21956b

> 
> > You should also look at the transplant extension.
> 
> Ok, I will have a look at this.

Mr. Hostens' e-mail had a pretty straight-forward solution, too.