From: Martin Langhoff <martin.langhoff@gmail.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: tracking un-committed patches in mailing list?
Date: Sat, 8 May 2010 07:01:06 -0400 [thread overview]
Message-ID: <l2u46a038f91005080401vf3e5b16t9fe26be5cd5baf92@mail.gmail.com> (raw)
In-Reply-To: <p2obe6fef0d1005080332k26621c2fw48ea2482e84202dd@mail.gmail.com>
On Sat, May 8, 2010 at 6:32 AM, Tay Ray Chuan <rctay89@gmail.com> wrote:
> AFAIK, except for the authors themselves of patches, I don't know of
> anything tracking them - well, that's my experience as a patch
I found it -- patchwork; see https://patchwork.kernel.org/
Not git specific, actually. But a damn good tool.
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
prev parent reply other threads:[~2010-05-08 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 17:44 tracking un-committed patches in mailing list? Martin Langhoff
2010-05-08 10:32 ` Tay Ray Chuan
2010-05-08 11:01 ` Martin Langhoff [this message]
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=l2u46a038f91005080401vf3e5b16t9fe26be5cd5baf92@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=rctay89@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).