From: Quy Tonthat <qtonthat@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-remote exclude
Date: Thu, 18 Jan 2007 02:14:57 +1100 [thread overview]
Message-ID: <45AE3D71.9020708@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701161214460.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Fine. Submit a patch. And if that patch makes git-fetch not as fragile as
> I expect it to do, I am not opposed to inclusion. I'll just not use that
> feature. And I'll still find your usage confused.
>
I have no doubt your opposition to inclusion is important here. But some people
would (out-of-fashion'ly/arrogantly/dont-care'ly) submit their patches
"just for fun", as they did in the olden days. (Not that old to me though).
Quy
next prev parent reply other threads:[~2007-01-17 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 14:57 [PATCH] git-remote exclude Quy Tonthat
2007-01-15 10:23 ` Johannes Schindelin
2007-01-15 11:55 ` Andy Parkins
2007-01-15 20:10 ` Jakub Narebski
2007-01-15 21:56 ` Junio C Hamano
2007-01-16 10:26 ` Andy Parkins
2007-01-16 11:16 ` Johannes Schindelin
2007-01-17 15:14 ` Quy Tonthat [this message]
2007-01-17 15:19 ` Johannes Schindelin
2007-01-17 14:13 ` Quy Tonthat
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=45AE3D71.9020708@gmail.com \
--to=qtonthat@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.