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

Re: Splitting the mailing list up

From
LPLeonid Podolny <leonidp.lists@gmail.com>
Date
Oct 2, 2010, 18:26 UTC
Message-ID
<AANLkTik-+5uCuRkEqE6_e5dcYsY8vhbX-qYXpaL2f9CP@mail.gmail.com>
In-Reply-To
<20100925230022.6e2fd389.coolzone@it.dk>
On Sat, Sep 25, 2010 at 11:00 PM, Rico Secada <coolzone@it.dk> wrote:
Show 5 quoted lines
> Hi all.
>
> Would it be a bad idea to split the Git mailing list up in several
> sub-categories?
>

As far as I can tell, splitting a list into -dev and -user lists tends to drive the quality of the -user list down. The people with actual knowledge about the topic ask themselves: "Why do I keep answering questions from clueless noobs, while all the action I care about happens on another list?" and end up leaving the list altogether. I think that as long as the traffic on this list remains manageable, we should keep everything as-is.

Previous: Sebastien DoucheNext: Adrian Buehlmann
Message 12 of 19 in “Splitting the mailing list up”
  1. Rico SecadaSep 25, 2010
  2. Ævar Arnfjörð BjarmasonSep 25, 2010
  3. Rico SecadaSep 25, 2010
  4. Jay SoffianSep 26, 2010
  5. walter harmsSep 26, 2010
  6. Sebastien DoucheSep 26, 2010
  7. Wincent ColaiutaSep 26, 2010
  8. Ævar Arnfjörð BjarmasonSep 26, 2010
  9. Nicolas SebrechtSep 27, 2010
  10. Adrian BuehlmannSep 28, 2010
  11. Sebastien DoucheSep 29, 2010
  12. Leonid PodolnyOct 2, 2010
  13. Adrian BuehlmannSep 29, 2010
  14. Michael J GruberSep 29, 2010
  15. Erik Faye-LundSep 29, 2010
  16. Adrian BuehlmannSep 29, 2010
  17. Erik Faye-LundSep 29, 2010
  18. Sverre RabbelierSep 29, 2010
  19. Brandon CaseyOct 2, 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.