From: Ramkumar Ramachandra <artagnon@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Remove some junk characters from COPYING
Date: Sat, 16 Jan 2010 09:22:27 +0530 [thread overview]
Message-ID: <f3271551001151952mb7b810ft2264dad92fb79099@mail.gmail.com> (raw)
In-Reply-To: <20100115222811.GB18878@gmail.com>
Hi,
> http://git.or.cz/gitwiki/GitTips#Usingmsmtptosendyourpatches
Thank you for the link! Yes, I know about git send-imap, but I my
firewall blocked traffic on all ports except 80 and 443 until
yesterday. I jumped some hoops and got a few more ports opened up for
myself yesterday, so no more attachments in Gmail :)
> I'm sure there are other ways, but that's the one that works for
> me. I also use mutt to read gmail; also highly recommended :)
In that case, check out Sup. It's *much* better than mutt :)
next prev parent reply other threads:[~2010-01-16 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 8:22 [PATCH] Remove some junk characters from COPYING Ramkumar Ramachandra
2010-01-15 22:28 ` David Aguilar
2010-01-16 3:52 ` Ramkumar Ramachandra [this message]
2010-01-16 1:09 ` Robin Rosenberg
2010-01-16 4:00 ` Ramkumar Ramachandra
2010-01-16 5:38 ` 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=f3271551001151952mb7b810ft2264dad92fb79099@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
/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).