[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] 1.6 Release Engineering

From: Lyndon Nerenberg
Subject: Re: [Nmh-workers] 1.6 Release Engineering
Date: Fri, 7 Mar 2014 19:02:30 -0800

On Mar 7, 2014, at 5:53 PM, Ken Hornstein <address@hidden> wrote:

> One shows up under "git tag".  The other shows up under "git branch".
> Assuming we do annotated tags, you can even use git cat-file to
> distinguish between the two even easier.  I'm having a hard time
> understanding the problem.

In git, a tag is just a label on the hash for a particular commit.

A branch, OTOH, creates a cut point that becomes an anchor for diverted 

E.g, try this:

  git checkout nmh-1_3

You are now on an orphan branch -- git can't divert commits from the head based 
upon a single tag.

Undo this by saying 'git checkout master' to get back to the head.  Then, 'git 
checkout posix'.  Now you are in a part of the revision tree where you can play 
to your hearts content.

This is no different than the branch work you've been doing for the MIME header 
bits.  I'm just trying to formalize the naming scheme a bit better than has 
been done in the past.  And perhaps lay down some guidelines as to when to cut 
off commits in preparation for the release.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

reply via email to

[Prev in Thread] Current Thread [Next in Thread]