From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Steffen Prohaska <prohaska@zib.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Sixt <johannes.sixt@telecom.at>,
msysGit <msysgit@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Should we discuss Windows-related changes on git@vger.kernel.org?
Date: Fri, 11 Jul 2008 16:06:57 -0700 [thread overview]
Message-ID: <7vmykohvfy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0807112226190.8950@racer> (Johannes Schindelin's message of "Fri, 11 Jul 2008 22:38:23 +0100 (BST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> And if the separation is not always that clear, why not discuss those
> things on msysGit first, and then come to git@vger with our minds (and
> possibly our patches) made up?
I know you mean well, but my impression from reading the kernel list is
that often a message that says "we already debated this issue on our list
to death and here is our conclusion, take it or leave it" to the audience
is not accepted warmly, and more central kernel people may even say "do
not hide the discussion in the subsystem list, do it in the open,
discussion on the subsystem list does not matter".
Taking that lesson from the other community, I'd suggest that it is
probably a good idea to start discussion on your list, but once (some)
people in the discussion think the topic is releavant here, move it here
sooner rather than later.
next prev parent reply other threads:[~2008-07-11 23:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 8:07 Should we discuss Windows-related changes on git@vger.kernel.org? Steffen Prohaska
2008-07-11 11:56 ` Johannes Schindelin
2008-07-11 15:51 ` Steffen Prohaska
2008-07-11 15:57 ` Johannes Schindelin
2008-07-11 16:24 ` Steffen Prohaska
2008-07-11 18:36 ` Johannes Schindelin
2008-07-11 19:04 ` Linus Torvalds
2008-07-11 19:40 ` Johannes Schindelin
2008-07-11 21:10 ` Steffen Prohaska
2008-07-11 21:38 ` Johannes Schindelin
2008-07-11 23:06 ` Junio C Hamano [this message]
2008-07-11 23:37 ` Johannes Schindelin
2008-07-12 8:07 ` Steffen Prohaska
2008-07-11 22:14 ` Junio C Hamano
2008-07-11 23:35 ` Johannes Schindelin
2008-07-11 23:40 ` Linus Torvalds
2008-07-11 23:47 ` Johannes Schindelin
2008-07-11 23:58 ` Linus Torvalds
2008-07-12 0:06 ` Johannes Schindelin
2008-07-12 1:07 ` Linus Torvalds
2008-07-12 7:38 ` Steffen Prohaska
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=7vmykohvfy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=johannes.sixt@telecom.at \
--cc=msysgit@googlegroups.com \
--cc=prohaska@zib.de \
--cc=torvalds@linux-foundation.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