git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: Are more and more patches getting lost lately?
Date: Wed, 03 Sep 2008 21:34:19 -0700	[thread overview]
Message-ID: <7vd4jk8r78.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080904083343.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Thu, 04 Sep 2008 08:33:43 +0900")

Nanako Shiraishi <nanako3@lavabit.com> writes:

> I noticed that recently there are many patches sent to the list
> that are left unapplied (and many of them are from you).  Many
> of them look useful or at least promising to become useful.

Geez.  Well,... thanks.

Do you have particular ones in the list that you really want to see
in-tree early, do you want all of them, or what?

> What can we, the mailing list readers, do to help these patches
> applied?  Ask the authors of individual patches about their
> progress?

That would be the way to go.  I try to comment on all patches/topics that
interests me, and I refrain from applying what I commented on before I see
responses (and the response should not be "yes sir I'll obey blindly";
"No, the reason I did it that way was because..." to show that the
submitter has thought things through is much more preferred).  If there is
no progress in the discussion, it is very possible that I forget, even
when it is my turn to respond.  "I defended my position responding to
comments from you [or from the list] and I believe my argument was sound.
Did you forget to apply the patch, or do you want to discuss more?" from
the original submitter is very much appreciated.

  reply	other threads:[~2008-09-04  4:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 23:33 Are more and more patches getting lost lately? Nanako Shiraishi
2008-09-04  4:34 ` Junio C Hamano [this message]
2008-09-04  8:20 ` Nanako Shiraishi
2008-09-04  8:30   ` Imran M Yousuf
2008-09-04  8:45     ` Junio C Hamano
2008-09-04  9:00   ` Junio C Hamano
2008-09-04 16:58 ` Brandon Casey

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=7vd4jk8r78.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nanako3@lavabit.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).