git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Matt Graham" <mdg149@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: Patrick.Higgins@cexp.com, git@vger.kernel.org
Subject: Re: git branch diagram
Date: Mon, 21 Apr 2008 08:48:46 -0400	[thread overview]
Message-ID: <1c5969370804210548q4b6aa30h8a8c0323b3fc51d4@mail.gmail.com> (raw)
In-Reply-To: <m3fxtgqcbr.fsf@localhost.localdomain>

On Sun, Apr 20, 2008 at 8:30 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> <Patrick.Higgins@cexp.com> writes:
>
>  > In my diagram, I am assuming that most developers work in master,
>  > and make branches for their own long-lived projects and experimental
>  > things.
>
>  For example git itself, as a project, uses three long-lived branches:
>  'maint', 'master' and 'next', uses 'pu' (proposed updates) branch as
>  propagation / review mechanism for short-lived tipic branches.

Jakub, could you explain the difference between maint and master?  And
the difference between master and next?  Maint and next are clear, but
how does master relate to those 2?

  reply	other threads:[~2008-04-21 12:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 17:00 git branch diagram Patrick.Higgins
2008-04-18  1:38 ` Sitaram Chamarty
2008-04-18  2:29 ` Roman V. Shaposhnik
2008-04-18  6:46 ` Karl Hasselström
2008-04-18  8:39 ` Fedor Sergeev
2008-04-18 13:07 ` Matt Graham
2008-04-21  0:30 ` Jakub Narebski
2008-04-21 12:48   ` Matt Graham [this message]
2008-04-21 13:06     ` Jakub Narebski
2008-04-21 13:07     ` Luciano Rocha

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=1c5969370804210548q4b6aa30h8a8c0323b3fc51d4@mail.gmail.com \
    --to=mdg149@gmail.com \
    --cc=Patrick.Higgins@cexp.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).