Re: confused by git release tags

Hello James,

On Nov 9, 2013, at 18:29 , James Cloos wrote:

>>>>>> "PvD" == Peter van Dijk <[email protected]> writes:
> 
> PvD> When we release minor versions (like 3.5.1-3.5.3), this is our process (described based on 3.5.3):
> PvD> - create a branch rel/rec-3.5.3 off of the rec-3.5.2 tag
> 
> Perhaps those rel/ branches should be pushed to the github repo?
> 
> As it is (checked on a fresh clone), the only rel/ branch available is
> remotes/origin/rel/auth-3.3.1.


The rel/ branches live in our github repo until we tag their head; then we remove them. I figured a tag would be just as good.

If there is demand, I'm happy to reinstate the rel/ branches for the tags that have been generated from one, and to stop removing them in the future. It would help if I understood what use case we are fixing with it, though :)

Kind regards,
-- 
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/

_______________________________________________
Pdns-dev mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-dev

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJSfnWfAAoJENz1E/p+7RnzPjAP+QFJbIzGSvfrmEx9jCNTa1hy
m0iIezEMz4cujijZGIK1ATVtYH78zHsFq9ZLKPLrdFbet33U3Vcc8C6NMR2BMFHk
9GyBCVWGPu7HPsRF+jIdjzdd1usQqt9+J3cpyiz52nrnkP+grvyB3jNyQI/Fzd1N
VytTa2Ealvvjy2nDeCzC6BdQxRii/CSRCCHcoQPEpkvimYyNKgA2rC2nmUQ4wQGc
XoN5AqZBx0szETSvjJvW/N2thIaXYpG8wzfxVr7JRNyX+N5WDP+Wh20MSxnq74tg
KvsxKPzDfILYvMuFB7lkSNk1016N1kw0mhjTZfIbNFK7Hj1OJJOBE4jMTwcskz4l
J3mXrsdjraMHSloXHADrDK1ikt3dkzu2hzL3w2CXr9NsmTkqd+ENAhgra4AQAVoA
kTV3tCVn1IMwl2gwt/phTZstMTxyba3B0tC2r0GtjZ0pJ8HDhNizK3AbPPb4RSKm
4zuQ36aA84hQF99xWxMUJ6D5uKiUt86pz7nI72bgqq+MP0CxKLBCaF8KJqx66CVN
qIwjToWsBnpZnLhLsHJnEkYN8+nvhuz5TatiBRfFnjG9IFAwNS91Rivbftjdia83
Or9v6nUTK4EnlJewyraKrewyezAKoQ6G0vDLWx8b8E1AsDpdG6jkQ8dE+0O0dY7G
jEo0CcPnRg4kj0pNDbaT
=lAlc
-----END PGP SIGNATURE-----