remove a branch from a repo

William Dode wilk-ml at flibuste.net
Wed Sep 27 21:48:35 BST 2006


On 27-09-2006, John Arbash Meinel wrote:
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --------------enig54841D90CA64DB84DD2588FD
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> William Dode wrote:
>>
>
>=2E..
>
>>> We've talked about garbage collection a lot. And it is pretty easy to
>>> implement. The biggest issue is that destroying history is not somethi=
> ng
>>> to do lightly. So it gets low priority from us, because it isn't
>>> something that you want to mess up, and isn't super critical for prope=
> r
>>> functioning.
>>>
>>> I have what needs to be done mapped out in my head, and if someone is
>>> interested in implementing it, I can go over it with them. I could wri=
> te
>>> up a spec one day, just hasn't been worth the time yet.
>>>
>>> So William, how important is this for you?
>>=20
>> Thank you but it's not actualy important for me, i just pointed this=20
>> because when we read the tutorials about repository it really miss=20
>> something, specialy whith example of branch to correct one bug. The=20
>> shared repository are specialy interesting for big tree, so people will=
>=20
>> think about this.
>
> Well if you are branching to fix a bug, and then merge that into the
> source. You still have that revision in the ancestry, so you *don't*
> want to get rid of it anyway.

I didn't know that a repository was already so much optimized !
So it's realy safe and clean for a shared repository to remove a tree of 
a branch after a merge.

-- 
William Dodé - http://flibuste.net





More information about the bazaar mailing list