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, 01:19 UTC
Message-ID
<46a038f90609021819v6d427f0eh69bc13b30ef6b692@mail.gmail.com>
In-Reply-To
<9e4733910609020731k25ce3a0aw7a84542f8cd516f6@mail.gmail.com>
On 9/3/06, Jon Smirl <jonsmirl@gmail.com> wrote:
> The Mozilla people have a web page describing what they are looking
> for in a new version control system. How does git stack up?
Hi Jon,

you've been playing with GIT quite a bit by now, so I guess you know the answer ;-) Is there anything in particular you are wondering about?

The one item that sticks out for me as not there is ACLs, but access controls can be implemented in hooks for direct pushes. Maintain an .htaccess-like file and have a perl script to check it on pushes to the repo.

Oh, and "partial tree pulls for localisers". Perhaps git-cvsserver can help there? Localisers can just use TortoiseCVS and get a checkout of the language pack subdir.

cheers,
martin
-- 
VGER BF report: U 0.544429
Previous: Jon SmirlNext: Jon Smirl
Message 2 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.