git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Orsila <shdl@zakalwe.fi>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jakub Narebski <jnareb@gmail.com>, Petr Baudis <pasky@suse.cz>,
	msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [msysGit] [FYI][PATCH] Customizing the WinGit installer
Date: Tue, 7 Oct 2008 10:46:42 +0300	[thread overview]
Message-ID: <20081007074642.GK16289@zakalwe.fi> (raw)
In-Reply-To: <20081007030824.GW21650@dpotapov.dyndns.org>

On Tue, Oct 07, 2008 at 07:08:24AM +0400, Dmitry Potapov wrote:
> On Mon, Oct 06, 2008 at 07:10:37PM -0700, Linus Torvalds wrote:
> > 
> > That changes things. Once some user actually complains, and sends in a 
> > fix to make the whole dialog optional, I don't see why anybody would ever 
> > argue against such a patch being accepted.
> 
> First, he did not complain. He did not even mention that in the commit
> message.

What does that matter? People are complaining now.

> He mentioning some other things like removing release notes,
> but not the license. Second, I would expect that any change that goes
> against the previous achieved agreement may deserve some discussion,
> and not blindly accepted just because the user sent a patch.

Are you thinking this is some kind of decision by committee 
organization? NO. Patches are picked up by maintainers. Anyone can 
comment on the patches as they are published.

> Okay, I
> don't really care whether the installer shows the license or not...

Then why argue about it? I care very much.

-- 
Heikki Orsila
heikki.orsila@iki.fi
http://www.iki.fi/shd

  reply	other threads:[~2008-10-07  7:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 12:27 [FYI][PATCH] Customizing the WinGit installer Petr Baudis
2008-10-06 14:22 ` [msysGit] " Johannes Schindelin
2008-10-06 14:18   ` Petr Baudis
2008-10-06 15:23     ` Johannes Schindelin
2008-10-06 16:00       ` Jakub Narebski
2008-10-06 16:12         ` Johannes Schindelin
2008-10-06 17:34           ` Linus Torvalds
2008-10-06 17:51             ` Bruce Stephens
2008-10-06 17:54             ` Robin Burchell
2008-10-06 18:01             ` Johannes Schindelin
2008-10-06 19:47               ` [msysGit] " Linus Torvalds
2008-10-07  1:53                 ` Dmitry Potapov
2008-10-07  2:10                   ` Linus Torvalds
2008-10-07  3:08                     ` Dmitry Potapov
2008-10-07  7:46                       ` Heikki Orsila [this message]
2008-10-07  9:28                     ` [msysGit] " Petr Baudis
2008-10-08  7:38                       ` Junio C Hamano
2008-10-06 20:11               ` [msysGit] " Heikki Orsila
2008-10-07  1:59                 ` Dmitry Potapov
2008-10-07  2:40                   ` Avery Pennarun
2008-10-07  7:42                   ` Heikki Orsila
2008-10-06 21:19               ` Abdelrazak Younes
2008-10-06 17:23       ` Petr Baudis

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=20081007074642.GK16289@zakalwe.fi \
    --to=shdl@zakalwe.fi \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=msysgit@googlegroups.com \
    --cc=pasky@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).