All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Raman Gupta <rocketraman@fastmail.fm>, git@vger.kernel.org
Subject: Re: Reference for git.git release process
Date: Thu, 26 Mar 2009 09:05:58 +0100	[thread overview]
Message-ID: <49CB3766.5090109@op5.se> (raw)
In-Reply-To: <7viqlxz9go.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote:
> 
> In addition, you can keep older maintenance track around, i.e.
> 
> 	git branch maint-X.Y.(Z-1) maint
>         git checkout maint
>         git merge master
> 
> so that maintenance releases for even older codebase _could_ be issued
> _if_ necessary.
> 

Assuming one tags ones releases (which one should, and git.git does),
creating maint-X.Y.Z when it's actually needed is a far better approach.

No morning coffee yet, Junio? ;-)

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

  parent reply	other threads:[~2009-03-26  8:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 18:32 Reference for git.git release process Raman Gupta
2009-03-25 19:30 ` Junio C Hamano
2009-03-25 22:03   ` Raman Gupta
2009-03-25 23:41     ` Junio C Hamano
2009-03-26  3:26       ` Junio C Hamano
2009-03-26  2:27   ` Jeff King
2009-03-26  3:13     ` Junio C Hamano
2009-03-26  3:15       ` Jeff King
2009-03-26  3:28         ` Junio C Hamano
2009-03-26  3:49           ` Jeff King
2009-03-26  3:34     ` Junio C Hamano
2009-03-26 17:03       ` Shawn O. Pearce
2009-03-26  8:05   ` Andreas Ericsson [this message]
2009-03-26 14:29     ` Raman Gupta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49CB3766.5090109@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rocketraman@fastmail.fm \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.