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

Re: Can I enforce required approval on some files

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 21, 2010, 07:51 UTC
Message-ID
<201007210951.25150.jnareb@gmail.com>
In-Reply-To
<AANLkTilWzSU9Uh0QT5CcauXiiBKtkG37To57s6zUxzDK@mail.gmail.com>
On Wed, 21 Jul 2010, Ævar Arnfjörð Bjarmason wrote:
Show 10 quoted lines
> On Tue, Jul 20, 2010 at 22:03, Jakub Narebski <jnareb@gmail.com> wrote:
> 
> > Besides solution mentioned by others, namely integration repository
> > with moderator, you can also use patch/commit code review tool such as
> > Gerrit (http://code.google.com/p/gerrit/), equivalent of Rietveld for
> > Subversion, or Mondrian for Perforce.
> 
> There's also the low-tech solution of just telling people to submit
> again until their patches don't suck, it works for git.git, and is
> attainable when you're not doing a centralized tool.

That's what I meant by "besides [...] integration repository with moderator", moderator who reviews patches or pull requests, and accepts into integration repository or rejects them.

-- 
Jakub Narebski
Poland
Previous: Ævar Arnfjörð Bjarmason
Message 6 of 6 in “Can I enforce required approval on some files”
  1. Dominik GrontJul 20, 2010
  2. Bruce StephensJul 20, 2010
  3. Sylvain RabotJul 20, 2010
  4. Jakub NarebskiJul 20, 2010
  5. Ævar Arnfjörð BjarmasonJul 21, 2010
  6. Jakub NarebskiJul 21, 2010

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.