Re: Emacs branches in git

[Dmitry Gutov]

Bill Wohler <address@hidden> writes:

>>> Please see http://nvie.com/posts/a-successful-git-branching-model/ for
>>> the rationale.

I don't see any justification there, except "We consider origin/master
to be ... a production-ready state." Which is just an arbitrary opinion.

>>> Also, in git, release branches are deleted when they are
>>> no longer needed.

So what? Tags can live on.

>> 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.

If master is to be used "for tagged releases", all release-tagged
revisions have to be able to line up in one branch. Interspersed with
plain revisions, of course.

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

Yes, and why do we need that? If one wants to use the latest release,
they can just fetch the list of tags, and then checkout the one with the
greatest number.

>> 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?

Yes, please.