From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Avoid perl in t1300-repo-config
Date: Thu, 28 Jun 2007 11:28:09 +0200 [thread overview]
Message-ID: <f5vuv9$f8s$1@sea.gmane.org> (raw)
In-Reply-To: 81b0412b0706280041i535efdf0r87e552551b796044@mail.gmail.com
Alex Riesen wrote:
>> By the way, is it possible for gmail users to avoid attachments
>> when sending patches in?
>
> No. The message text is unpredictably garbled
If by "gmail users" you mean gmail web interface, then probably no.
No problems with using gmail from email client or from git-send-email
(the latter after configuring sendmail in my case).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-06-28 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 12:45 [PATCH] Avoid perl in t1300-repo-config Alex Riesen
2007-06-27 15:15 ` Frank Lichtenheld
2007-06-27 15:47 ` Alex Riesen
2007-06-28 4:30 ` Junio C Hamano
2007-06-28 7:41 ` Alex Riesen
2007-06-28 8:56 ` Alex Riesen
2007-06-28 9:28 ` Jakub Narebski [this message]
2007-06-28 11:00 ` Alex Riesen
2007-06-28 14:19 ` Johannes Schindelin
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='f5vuv9$f8s$1@sea.gmane.org' \
--to=jnareb@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).