From: Sverre Rabbelier <srabbelier@gmail.com>
To: Erik Faye-Lund <kusmabite@googlemail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, Jeff King <peff@peff.net>,
Erik Faye-Lund <kusmabite@gmail.com>
Subject: Re: [PATCH 1/8] imap-send: remove useless uid code
Date: Fri, 9 Oct 2009 17:21:59 +0200 [thread overview]
Message-ID: <fabb9a1e0910090821n67c86d0kb4eef1b9ff4bdff1@mail.gmail.com> (raw)
In-Reply-To: <1255100682-13952-1-git-send-email-kusmabite@gmail.com>
Heya,
On Fri, Oct 9, 2009 at 17:04, Erik Faye-Lund <kusmabite@googlemail.com> wrote:
Please include a cover letter for series as long as these (anything
larger than 4 should have a cover letter IMHO). Doing so makes it
easier for those that follow the series to see what changed (assuming
you write down what changed in the cover letter). Also, it makes it
easier for those that were not following the series to drop in at the
current version (assuming you provide a short summary of what the
series is about in the cover letter)..
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-10-09 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 15:04 [PATCH 1/8] imap-send: remove useless uid code Erik Faye-Lund
2009-10-09 15:04 ` [PATCH 2/8] imap-send: use separate read and write fds Erik Faye-Lund
2009-10-09 15:04 ` [PATCH 3/8] imap-send: use run-command API for tunneling Erik Faye-Lund
2009-10-09 15:04 ` [PATCH 4/8] imap-send: fix compilation-error on Windows Erik Faye-Lund
2009-10-09 15:04 ` [PATCH 5/8] imap-send: build imap-send " Erik Faye-Lund
2009-10-09 15:04 ` [PATCH 6/8] mingw: wrap SSL_set_(w|r)fd to call _get_osfhandle Erik Faye-Lund
2009-10-09 15:04 ` [PATCH 7/8] mingw: enable OpenSSL Erik Faye-Lund
2009-10-09 15:04 ` [PATCH 8/8] MSVC: Enable OpenSSL, and translate -lcrypto Erik Faye-Lund
2009-10-09 15:42 ` [PATCH 4/8] imap-send: fix compilation-error on Windows Matt Kraai
2009-10-09 15:21 ` Sverre Rabbelier [this message]
2009-10-09 16:12 ` [PATCH 1/8] imap-send: remove useless uid code Erik Faye-Lund
2009-10-10 0:57 ` Junio C Hamano
2009-10-09 15:46 ` Matt Kraai
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=fabb9a1e0910090821n67c86d0kb4eef1b9ff4bdff1@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@gmail.com \
--cc=kusmabite@googlemail.com \
--cc=peff@peff.net \
/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).