Re: Emacs branches in git

[Bill Wohler]

David Kastrup <address@hidden> writes:

> Bill Wohler <address@hidden> writes:
>
>> Dmitry Gutov <address@hidden> writes:
>>
>>> Bill Wohler <address@hidden> writes:
>>>
>>>> master: For tagged releases.
>>>>
>>>> dev: How trunk is used now.
>>>
>>> Why is that?
>>>
>>> 1. People can put tags on revisions in release branches. Why dedicate a
>>> branch just for release tags?
>>
>> Please see http://nvie.com/posts/a-successful-git-branching-model/ for
>> the rationale. Also, in git, release branches are deleted when they are
>> no longer needed.
>
> You are talking past each other.  You want to organize tags into a
> directory of tags,

s/tags/branches/

> Dmitry is talking about placing tags all into a
> single branch.  Which makes very little sense.

Except that's not the point, but rather a side-effect. The point is that
master holds the production-ready commits.

>  But it's not obvious to
> casual users of gits that you can have tags in a directory structure
> that has nothing to do with either the work directory or the commit
> tree.

Can you expound on that?

-- 
Bill Wohler <address@hidden> aka <address@hidden>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD