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: Thu, 04 Sep 2008 02:00:27 -0700	[thread overview]
Message-ID: <7v8wu85lqs.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080904172059.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Thu, 04 Sep 2008 17:20:59 +0900")

Nanako Shiraishi <nanako3@lavabit.com> writes:

> Quoting Junio C Hamano <gitster@pobox.com>:
>
>> 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?
>
> Your "diff --quiet" and Petr's bash completion.

I do not recall what the status of "diff --quiet" thing was when the
discussion petered off.  I'll have to dig it up later.

I've queued the bash completion from Pasky.

> Also there are many patches that are from *you*.  Did you forget to apply
> them, are they buggy, or are they in any way bad?
>
> From: Junio C Hamano <gitster@pobox.com>
> Subject: Re: [PATCH] Enable git rev-list to parse --quiet
> Date: Thu, 17 Jul 2008 23:10:19 -0700
> Message-ID: <7vy73zd8ok.fsf@gitster.siamese.dyndns.org>
>
> http://article.gmane.org/gmane.comp.version-control.git/88994

Be reasonable -- that's more than 5 minutes ago.

'rev-list --check-empty $args' would be equivalent to 'test -z "$(rev-list
-1 $args)"'; I am not interested in it myself, and original requestor went
away.  I have been assuming that it is not worth our time to worry about
it if the change is not even necessary by somebody who brought it up
originally.

> From: Junio C Hamano <gitster@pobox.com>
> Subject: [PATCH/RFC] feeding Maildir to git-am
> Date: Tue, 19 Aug 2008 22:25:57 -0700
> Message-ID: <7vbpzotfyy.fsf@gitster.siamese.dyndns.org>
>
> http://article.gmane.org/gmane.comp.version-control.git/92963

I wanted to see more positive feedback or better alternatives from people
who do deal with Maildir, especially because I do not use Maildir
anywhere.  Again, the discussion seems to have petered out, so...

> From: Junio C Hamano <gitster@pobox.com>
> Subject: Re* [PATCH] git-apply - Add --include=PATH
> Date: Mon, 25 Aug 2008 01:05:31 -0700
> Message-ID: <7vhc99h644.fsf@gitster.siamese.dyndns.org>
>
> http://article.gmane.org/gmane.comp.version-control.git/93604

IIRC, the patch was in a good shape but without documentation and tests.
I suspect reassembling the pieces from the mailing list archive into an
appliable e-mail submission would have been trivial, if somebody cared
deeply enough, but nothing came out of it.

  parent reply	other threads:[~2008-09-04  9:01 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
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 [this message]
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=7v8wu85lqs.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).