From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/9] transport-helper: updates
Date: Thu, 29 Aug 2013 14:26:40 -0500 [thread overview]
Message-ID: <CAMP44s2jG8aD66uhiB9a0HYGro1p7yHkMJ4+XmzQD+a6f42QhA@mail.gmail.com> (raw)
In-Reply-To: <xmqqwqn42tgb.fsf@gitster.dls.corp.google.com>
On Thu, Aug 29, 2013 at 2:22 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> Some of these were were sent before and rejected without a
>> reason,...
>
> Earlier, you were asked to leave because many constructive criticism
> or suggestion for improvement to your patches in reviews led to
> stubborn resistance, ended up wasting everybody's time and left a
> bad atmosphere on the list.
>
> It seems that Matthew is trying to see if you can work better with
> others than before after a break, but I personally am not hopeful
> yet and do not want to waste my/our time on flamewars like we saw in
> the past.
>
> So I'll look at these and may pick patches that are obviously and
> trivially good, but will refrain from asking clarifications and
> suggesting improvements, etc. on other patches that I suspect will
> end up wasting the time of people again. Do not take silence from
> me as a silent agreement.
If you do not pick these patches, the only one that looses is the Git
project and its users.
--
Felipe Contreras
next prev parent reply other threads:[~2013-08-29 19:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 15:23 [PATCH 0/9] transport-helper: updates Felipe Contreras
2013-08-29 15:23 ` [PATCH 1/9] transport-helper: add 'force' to 'export' helpers Felipe Contreras
2013-09-23 2:41 ` Richard Hansen
2013-09-23 2:39 ` Felipe Contreras
2013-08-29 15:23 ` [PATCH 2/9] transport-helper: check for 'forced update' message Felipe Contreras
2013-08-29 15:23 ` [PATCH 3/9] fast-export: improve argument parsing Felipe Contreras
2013-08-29 15:23 ` [PATCH 4/9] fast-export: add new --refspec option Felipe Contreras
2013-09-23 1:59 ` Richard Hansen
2013-09-23 2:35 ` Felipe Contreras
2013-08-29 15:23 ` [PATCH 5/9] transport-helper: add support for old:new refspec Felipe Contreras
2013-08-29 15:23 ` [PATCH 6/9] fast-import: add support to delete refs Felipe Contreras
2013-08-29 15:23 ` [PATCH 7/9] fast-export: " Felipe Contreras
2013-08-29 15:23 ` [PATCH 8/9] transport-helper: add support to delete branches Felipe Contreras
2013-09-23 1:50 ` Richard Hansen
2013-09-23 2:34 ` Felipe Contreras
2013-08-29 15:23 ` [PATCH 9/9] transport-helper: don't update refs in dry-run Felipe Contreras
2013-08-29 19:22 ` [PATCH 0/9] transport-helper: updates Junio C Hamano
2013-08-29 19:26 ` Felipe Contreras [this message]
2013-09-23 1:49 ` Richard Hansen
2013-09-23 2:32 ` 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=CAMP44s2jG8aD66uhiB9a0HYGro1p7yHkMJ4+XmzQD+a6f42QhA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).