git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git branch diagram

From
Matt Graham <mdg149@gmail.com>
Date
Apr 21, 2008, 12:48 UTC
Message-ID
<1c5969370804210548q4b6aa30h8a8c0323b3fc51d4@mail.gmail.com>
In-Reply-To
<m3fxtgqcbr.fsf@localhost.localdomain>
On Sun, Apr 20, 2008 at 8:30 PM, Jakub Narebski <jnareb@gmail.com> wrote:
Show 9 quoted lines
> <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?

Previous: Jakub NarebskiNext: Jakub Narebski
Message 8 of 10 in “git branch diagram”
  1. patrick.higgins@cexp.comApr 17, 2008
  2. Sitaram ChamartyApr 18, 2008
  3. Roman V. ShaposhnikApr 18, 2008
  4. Karl HasselströmApr 18, 2008
  5. Fedor SergeevApr 18, 2008
  6. Matt GrahamApr 18, 2008
  7. Jakub NarebskiApr 21, 2008
  8. Matt GrahamApr 21, 2008
  9. Jakub NarebskiApr 21, 2008
  10. Luciano RochaApr 21, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.