git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Adrian Buehlmann <adrian@cadifra.com>
Cc: Kevin Ballard <kevin@sb.org>, Rico Secada <coolzone@it.dk>,
	git@vger.kernel.org
Subject: Re: Splitting the mailing list up
Date: Wed, 29 Sep 2010 11:08:17 +0200	[thread overview]
Message-ID: <4CA30201.5020006@drmicha.warpmail.net> (raw)
In-Reply-To: <4CA2FA76.6080501@cadifra.com>

Adrian Buehlmann venit, vidit, dixit 29.09.2010 10:36:
> On 28.09.2010 22:06, Kevin Ballard wrote:
>> On Sep 27, 2010, at 11:22 PM, Adrian Buehlmann wrote:
>>
>>> I think this would definitely be an improvement for git users. At least
>>> splitting up into dev and user, like Mercurial does it too (which I am
>>> used to). Not sure about announce though.
>>>
>>> When I recently subscribed to this list (after having been a long time
>>> subscriber to the Mercurial lists too), I was interested in seeing
>>> discussions about git usage to help me get started with git.
>>>
>>> I also think searching the archives would be a bit easier if discussions
>>> of new git development details and its usage would be separated.
>>
>> Perhaps it would make more sense to simply create a new list for git
>> newbies to get help, and to not change the nature of this existing list
>> at all.
> 
> Of course, I would be fine if this list here would be simply defined as
> the "git development centric list" and a new, more usage-centric list
> could be started (git-users ?).

You mean something like:

git-users@googlegroups.com

I don't participate there, but my impression is that it's really a user
group.

FWIW: When I was new, the volume over here was too much for me also, and
simply filtering out all PATCH messages was a perfect solution. I've
removed that filter meanwhile, though...

Michael

  reply	other threads:[~2010-09-29  9:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25 21:00 Splitting the mailing list up Rico Secada
2010-09-25 21:05 ` Ævar Arnfjörð Bjarmason
2010-09-25 21:19   ` Rico Secada
2010-09-26  6:52     ` Jay Soffian
2010-09-26 15:58 ` walter harms
2010-09-26 16:02 ` Sebastien Douche
2010-09-26 17:30   ` Wincent Colaiuta
2010-09-26 18:54     ` Ævar Arnfjörð Bjarmason
2010-09-27 16:53       ` Nicolas Sebrecht
2010-09-28  6:22 ` Adrian Buehlmann
2010-09-29  7:56   ` Sebastien Douche
     [not found]   ` <141CAFB5-D423-48FE-BEED-B755C5F2685B@sb.org>
2010-09-29  8:36     ` Adrian Buehlmann
2010-09-29  9:08       ` Michael J Gruber [this message]
2010-09-29 13:00         ` Erik Faye-Lund
2010-09-29 13:20           ` Adrian Buehlmann
2010-09-29 13:30             ` Erik Faye-Lund
2010-09-29 15:02           ` Sverre Rabbelier
2010-10-02 21:33             ` Brandon Casey
2010-10-02 18:26 ` Leonid Podolny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CA30201.5020006@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=adrian@cadifra.com \
    --cc=coolzone@it.dk \
    --cc=git@vger.kernel.org \
    --cc=kevin@sb.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).