From: Junio C Hamano <gitster@pobox.com>
To: Akira Kitada <akitada@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-patches list?
Date: Mon, 12 Jan 2009 15:54:22 -0800 [thread overview]
Message-ID: <7vr638f5ch.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 90bb445a0901121543q29d30d49yaa723b4b913a4b31@mail.gmail.com
Akira Kitada <akitada@gmail.com> writes:
> Can I propose having another mailing list for posting patches to avoid
> daily mail flood to this list?
>
> Yes, I can filter out the emails but still...
This list has always been the only place where git development happens.
It would make the development very awkward to set up another list only for
patches, forbid patches to be sent to anywhere but that new list, but
still discuss the patches on this list.
It does not make much sense to me.
Consider what you would do when you see a problem somebody is having on
this list, and wanted to respond with a quick "this may fix it" patch?
Should you be sending that to the patches list, and sending a separate
message to this list saying that you have a potential fix in mind you
would want to discuss here, but the patches list rule mandated that you
had to send the patch to the other list, asking people who are reading
this list to look at the other list as well?
And no, having a separate "user list" won't solve the above problem either
and that is not what I am suggesting.
Not that I am seeing any problem right now; I am saying that the split
list as you suggest _will_ create problems.
next prev parent reply other threads:[~2009-01-12 23:55 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 [this message]
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
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=7vr638f5ch.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=akitada@gmail.com \
--cc=git@vger.kernel.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).