From: "Jim Raden" <james.raden@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Tilman Schmidt" <tilman@imap.cc>,
"Martin Langhoff" <martin.langhoff@gmail.com>,
"Jakub Narebski" <jnareb@gmail.com>,
msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: The 8th airing of the msysGit herald
Date: Wed, 5 Mar 2008 21:03:27 -0500 [thread overview]
Message-ID: <5fc54b450803051803t4dda4341ue3ac403c742f1903@mail.gmail.com> (raw)
In-Reply-To: <7vskz4heeg.fsf@gitster.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]
Perhaps adopting a convention for the subject line, like "Usage question:
xxxxxxxxxxxxxxxxxxxxx"? We're still a small list, so it wouldn't be horribly
cumbersome. If the list grew beyond 150 or
so<http://en.wikipedia.org/wiki/Dunbar%27s_number>active users, or if
the signal:noise ratio grew too low, perhaps then that
would be a good time to readdress the issue.
I confess that I haven't had to deal with such things before, so I'm not
familiar with the practices that may work in other groups faced with a
similar issue.
On Wed, Mar 5, 2008 at 7:41 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Thu, 6 Mar 2008, Tilman Schmidt wrote:
> >
> >> would it be possible to have separate mailing lists for usage topics
> and
> >> for discussions of ongoing development? I imagine that might help those
> >> who just want to use git (like me) to find their way around.
> >
> > AFAIAC you can have your "users-only" mailing list. Personally, I will
> > never look at it, though, since all I am interested in is the
> development
> > of Git. If that holds true for the majority of Git _developers_, it
> might
> > even be a bad idea to have a separate users' list, since then
> >
> > - no ideas from strictly-users would flow to the developers, and
> >
> > - new developments would not reach you, and
> >
> > - you would not get help by the people knowing the internals _deeply_.
>
> Personally, I suspect I would end up subscribing to both, but
> two mailing lists would make it much more cumbersome than
> necessary to correlate the original user "itch" request that
> triggered an enhancement, the discussion that clarified the
> design constraints and requirements, and the patch and the
> review comments that lead to the final implementation,
> especially if you do not encourage cross posting to both lists.
> And of course cross posting will make user-only list more
> technical which would defeat the original point of having two
> lists.
>
> "users-only" list could probably created by readers' MUA, by
> picking emails that do not have "diff --git" in its body; that
> would probably be a good enough approximation for people who are
> not interested in the technical discussions.
>
[-- Attachment #2: Type: text/html, Size: 2827 bytes --]
next prev parent reply other threads:[~2008-03-06 2:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 23:30 The 8th airing of the msysGit herald Johannes Schindelin
2008-03-03 0:44 ` Jakub Narebski
2008-03-03 0:54 ` Johannes Schindelin
2008-03-03 1:10 ` Jakub Narebski
2008-03-03 12:00 ` Tilman Schmidt
2008-03-03 12:05 ` Johannes Schindelin
2008-03-03 18:21 ` Tilman Schmidt
2008-03-03 18:48 ` Brandon Casey
2008-03-05 23:12 ` Tilman Schmidt
2008-03-03 17:18 ` Junio C Hamano
2008-03-03 18:27 ` Tilman Schmidt
2008-03-03 22:37 ` Junio C Hamano
2008-03-03 22:58 ` Martin Langhoff
2008-03-05 23:40 ` Tilman Schmidt
2008-03-06 0:26 ` Johannes Schindelin
2008-03-06 0:41 ` Junio C Hamano
2008-03-06 2:03 ` Jim Raden [this message]
2008-03-06 2:29 ` Johannes Schindelin
2008-03-06 2:42 ` Jim Raden
2008-03-06 4:32 ` [msysGit] " Jay Soffian
2008-03-06 4:33 ` Jim Raden
2008-03-06 11:40 ` [msysGit] " Paul Franz
2008-03-06 4:29 ` Jay Soffian
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=5fc54b450803051803t4dda4341ue3ac403c742f1903@mail.gmail.com \
--to=james.raden@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=martin.langhoff@gmail.com \
--cc=msysgit@googlegroups.com \
--cc=tilman@imap.cc \
/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).