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

Re: Mozilla version control requirements and git

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Sep 3, 2006, 21:40 UTC
Message-ID
<46a038f90609031440s33e66499x51026aa6062566d2@mail.gmail.com>
In-Reply-To
<9e4733910609030646k6c722068m30f0e05fccc9c3c5@mail.gmail.com>
On 9/4/06, Jon Smirl <jonsmirl@gmail.com> wrote:
> You can't really fake it. Many of the projects in Mozilla are
> dependent on each other. If you break them up into separate
> repositories you lose the ability to do a cross project commit. This
> is common when you are changing an interface between the subprojects.

In many projects this is handled by having tags and generally versioning modules and interfaces. Being independent gives the subprojects/modules a lot more freedom to work/branch on wild tangents, and the versioned interfaces mean that -- with the contraints of the versioned interfaces -- you can mix and match branches/releases of the different subprojects.

In short, I'd definitely break those up :-)
cheers,
martin
-- 
VGER BF report: U 0.513231
Previous: Jakub NarebskiNext: Jon Smirl
Message 7 of 9 in “Mozilla version control requirements and git”
  1. Jon SmirlSep 2, 2006
  2. Martin LanghoffSep 3, 2006
  3. Jon SmirlSep 3, 2006
  4. Jakub NarebskiSep 3, 2006
  5. Jon SmirlSep 3, 2006
  6. Jakub NarebskiSep 3, 2006
  7. Martin LanghoffSep 3, 2006
  8. Jon SmirlSep 4, 2006
  9. Junio C HamanoSep 3, 2006

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.