From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "Petr Baudis" <pasky@suse.cz>, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH (homepage)] Make git homepage (main page) use valid HTML
Date: Fri, 30 Nov 2007 13:04:51 +0100 [thread overview]
Message-ID: <2c6b72b30711300404k441ff09dl126b61a906273e9f@mail.gmail.com> (raw)
In-Reply-To: <200711301255.57012.jnareb@gmail.com>
On Nov 30, 2007 12:55 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> Jonas Fonseca wrote:
> > BTW, the patch contained multiple wrapping problems. Don't know if
> > it is from your side or my broken use of GMail.
>
> I'm sorry, this was my mistake (forgot to turn off word wrapping when
> sending this patch). But as you have applied it, I don't need to
> resend, do I?
No.
--
Jonas Fonseca
prev parent reply other threads:[~2007-11-30 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 10:59 [PATCH (homepage)] Make git homepage (main page) use valid HTML Jakub Narebski
2007-11-30 11:42 ` Jonas Fonseca
2007-11-30 11:55 ` Jakub Narebski
2007-11-30 12:04 ` Jonas Fonseca [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=2c6b72b30711300404k441ff09dl126b61a906273e9f@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=pasky@suse.cz \
/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).