Re: fast-forward only policy

[Felipe Contreras <felipe contreras gmail com>]

On Wed, May 6, 2009 at 12:46 AM, Germán Póo-Caamaño <gpoo gnome org> wrote:
> On Wed, 2009-05-06 at 00:33 +0300, Felipe Contreras wrote:
>> On Tue, May 5, 2009 at 11:55 PM, Olav Vitters <olav bkor dhs org> wrote:
>> [...]
>> That's just how git works: branches and tags are mere pointers.
>> There's no difference in the object storage, the only difference is
>> logical, you use branches in a way, tags in another way.
>>
>> You can do stuff like:
>> git update-ref refs/heads/foobar 68b2aee # creates foobar branch
>> git update-ref refs/tags/foobar 68b2aee # creates foobar tag
>> git update-ref refs/taggybranch/foobar 68b2aee # creates foobar weird ref
>
> Are you assuming that all changes in stable branches get merged in
> development branches?
>
> How should it work the following development?
>
> a--a---a---a---a  (2-20)
>   +---b---b---b---b---b (2-22)
>           +---c---c---c---c---c---c (2-24)
>                   +---d---d---d---d---d---d---d--... (master)
>
> If delete the branch 2-22 I will loose the latest 3 commits, same for
> 2-20, and so on.

If you care about them, you'll make a tag that points to the head (and
make a release). If you have a tag, a branch, or any other reference
pointing to the commits then you'll never loose them (nor their
ancestors).

-- 
Felipe Contreras