From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
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: Sat, 12 Jul 2008 00:37:50 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807120036090.8950@racer> (raw)
In-Reply-To: <7vmykohvfy.fsf@gitster.siamese.dyndns.org>
Hi,
On Fri, 11 Jul 2008, Junio C Hamano wrote:
> 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".
I never meant on insisting that we find the final solution on the msysGit
list, and I would _never_ suggest that anything sent to git@vger is final.
It is always subject to discussion.
Anyway, enough said (since I think that you and me are in agreement here),
Dscho
next prev parent reply other threads:[~2008-07-11 23:38 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
2008-07-11 23:37 ` Johannes Schindelin [this message]
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=alpine.DEB.1.00.0807120036090.8950@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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