From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "Akira Kitada" <akitada@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: git-patches list?
Date: Wed, 14 Jan 2009 10:44:53 +0200 [thread overview]
Message-ID: <94a0d4530901140044t52af8536o805786718840f1d2@mail.gmail.com> (raw)
In-Reply-To: <90bb445a0901130755t6ea98bcco6b6663d806dcc2e6@mail.gmail.com>
On Tue, Jan 13, 2009 at 5:55 PM, Akira Kitada <akitada@gmail.com> wrote:
> This list seems to be used as a bug tracker, discussing git development,
> user questions, announcement etc.
> I thought this is so unusual list that something should be wrong here,
> but it turned out that it looks working right in mysteryous way.
> I take that back now.
> Hmm, interesting...
Yes, it's definitely not the norm on other projects, but perhaps it should be.
That's how the linux kernel mailing list works. There are other
mailing lists for the different sub-systems, but there's no separation
between bugs, discussion and patches, which makes sense, because quite
often bugs and patches trigger discussions, and bug discussions
trigger patches.
Following this approach perhaps it would make sense to create a
separate mailing list for jgit and similar stuff.
--
Felipe Contreras
prev parent reply other threads:[~2009-01-14 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 23:43 git-patches list? Akira Kitada
2009-01-12 23:54 ` Junio C Hamano
2009-01-13 8:26 ` Andreas Ericsson
2009-01-13 11:02 ` Johannes Schindelin
2009-01-19 4:29 ` Johannes Schindelin
2009-01-13 15:55 ` Akira Kitada
2009-01-14 8:44 ` Felipe Contreras [this message]
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=94a0d4530901140044t52af8536o805786718840f1d2@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=akitada@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).