From: Joe Perches <joe@perches.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Graham Barr <gbarr@pobox.com>
Subject: Re: [PATCH] git-send-email: Add AUTH LOGIN support
Date: Fri, 19 Aug 2011 16:24:40 -0700 [thread overview]
Message-ID: <1313796280.11178.25.camel@Joe-Laptop> (raw)
In-Reply-To: <7v1uwh0zj4.fsf@alter.siamese.dyndns.org>
On Fri, 2011-08-19 at 16:09 -0700, Junio C Hamano wrote:
> Joe Perches <joe@perches.com> writes:
> > I think my patch should be applied until Net::SMTP is updated.
> And you already have applied to your copy, no?
True.
> I do not necessarily agree with you that the patch _should_
> be applied to my tree.
Your choice. It does make tracking git development
a bit of a pain for me though.
There doesn't seem to be anything like a patchwork queue
for git development to check status of patches.
I've sent a couple of other patches to git-send-email.
http://marc.info/?l=git&m=131190328311281&w=2
http://marc.info/?l=git&m=131131975804893&w=2
Any comments or plans to ack/nack those?
next prev parent reply other threads:[~2011-08-19 23:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 0:40 [PATCH] git-send-email: Add AUTH LOGIN support Joe Perches
2011-08-06 4:54 ` Junio C Hamano
2011-08-06 5:21 ` Joe Perches
2011-08-19 1:16 ` Joe Perches
2011-08-19 23:09 ` Junio C Hamano
2011-08-19 23:24 ` Joe Perches [this message]
2011-08-20 1:01 ` Junio C Hamano
2011-09-24 15:49 ` [PATCH] send-email: auth plain/login fix Zbigniew Jędrzejewski-Szmek
2011-09-26 16:38 ` Junio C Hamano
2011-09-26 16:59 ` Joe Perches
2011-09-26 17:24 ` Jakub Narebski
2011-09-27 21:36 ` [PATCH v2] " Zbigniew Jędrzejewski-Szmek
2011-09-27 21:48 ` Jeff King
2011-09-28 10:26 ` [PATCH v3] " Zbigniew Jędrzejewski-Szmek
2011-09-28 22:00 ` Junio C Hamano
2011-09-29 14:16 ` [PATCH v4] " Zbigniew Jędrzejewski-Szmek
2011-09-29 15:01 ` Joe Perches
2011-09-29 17:02 ` [PATCH] " Zbigniew Jędrzejewski-Szmek
2011-09-29 18:12 ` Junio C Hamano
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=1313796280.11178.25.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=gbarr@pobox.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