From: Sverre Rabbelier <srabbelier@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
David Aguilar <davvid@gmail.com>,
git@vger.kernel.org, charles@hashpling.org,
markus.heidelberg@web.de
Subject: Re: [PATCH] Wait for git diff to finish in git difftool
Date: Thu, 23 Apr 2009 16:00:06 +0200 [thread overview]
Message-ID: <fabb9a1e0904230700l4c2123w663a2cfba65befcd@mail.gmail.com> (raw)
In-Reply-To: <81b0412b0904230252k3e8197d3y8798d5b797a49c39@mail.gmail.com>
Heya,
On Thu, Apr 23, 2009 at 11:52, Alex Riesen <raa.lkml@gmail.com> wrote:
> None. But it still would be nice if you look at them when you're addressed
> directly. Please understand, maybe I'm abusing the list a little, but it looks
> like the best place to _archive_ the workarounds for this obscure platform.
In that case you should note in your patch (preferrably in the
subject) that they are not meant for inclusion and merely for the that
purpose so that those who are not interested in them need not waste
their time reviewing the patch with the assumption that it _is_ meant
for inclusion.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-04-23 14:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 7:27 [PATCH] Wait for git diff to finish in git difftool Alex Riesen
2009-04-22 8:26 ` David Aguilar
2009-04-22 11:04 ` Alex Riesen
2009-04-22 18:59 ` Junio C Hamano
2009-04-22 20:40 ` Alex Riesen
2009-04-23 4:21 ` Junio C Hamano
2009-04-23 7:33 ` Alex Riesen
2009-04-23 8:26 ` Junio C Hamano
2009-04-23 9:52 ` Alex Riesen
2009-04-23 14:00 ` Sverre Rabbelier [this message]
2009-04-23 14:51 ` Junio C Hamano
2009-04-23 18:57 ` Alex Riesen
2009-04-23 19:08 ` Alex Riesen
2009-04-23 19:18 ` [PATCH] Explain seemingly pointless use of system in difftool Alex Riesen
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=fabb9a1e0904230700l4c2123w663a2cfba65befcd@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=charles@hashpling.org \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=markus.heidelberg@web.de \
--cc=raa.lkml@gmail.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).