From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: branchs and tags and merges oh my!
In-Reply-To: <87y60hn0mg.fsf@zancas.localnet>
References: <87y60hn0mg.fsf@zancas.localnet>
User-Agent: Notmuch/0.6 (http://notmuchmail.org) Emacs/23.3.1
	(x86_64-pc-linux-gnu)
Date: Sat, 02 Jul 2011 09:44:50 -0300
Message-ID: <87r568yhq5.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Fri, 01 Jul 2011 18:37:27 -0300, David Bremner <david@tethera.net> wrote:
>=20
> So now we have to decide what to do. FWIW, there are about 20 commits on
> release past d6f05fd.
>=20
> There are two obvious strategies going forward.
>=20

A third strategy is "git checkout master && git merge -s ours 0.6".=20
Then history will look like this:

  freeze=20=20=20=20=20=20=20
=2D-.-------------.----- master
   \           /
    -----------
               release

As long as every patch on the release branch is already on master, -s
ours (which throws away all the changes from the side branch) is
reasonable.

This has the advantage that "git describe master" starts to count from
0.6 instead of 0.5. Currently e.g. "make dist" on master is making
notmuch-0.5-317-gd15faa1.tar.gz. Unless we are going for the
"increasingly innacurately named" effect, that is probably not what we
want.

d

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iJwEAQECAAYFAk4PEsIACgkQTiiN/0Um85nlmAQAhEj4VRZ4vAPU18QO9Pf+/Qxa
Ox2JM//raYBp1U5EDbEOST3obON1ln5DD+/2ZEEqkcpwLs5cW+gGriAstfpqHriX
XlWtzoZ/tETVCBaTk8o/+6zNx9E5inIdKVfQMEz8oMi1zs0S9vln3Y7vOJKd6sVE
eswFZUbpoUKYJtHwpUc=
=mecS
-----END PGP SIGNATURE-----
--=-=-=--