git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: 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, 05 Mar 2008 16:41:59 -0800	[thread overview]
Message-ID: <7vskz4heeg.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0803060121360.15786@racer.site> (Johannes Schindelin's message of "Thu, 6 Mar 2008 01:26:58 +0100 (CET)")


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.

  reply	other threads:[~2008-03-06  0:42 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 [this message]
2008-03-06  2:03                       ` Jim Raden
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=7vskz4heeg.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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).