From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Hervé Cauwelier" <herve@itaapy.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/6] Open the pack file and keep a map on it.
Date: Wed, 14 Oct 2009 07:48:51 -0500 [thread overview]
Message-ID: <fabb9a1e0910140548g2ad99ec4ia0f4cd4cb6fc409c@mail.gmail.com> (raw)
In-Reply-To: <1255516669-26745-1-git-send-email-herve@itaapy.com>
Heya,
2009/10/14 Hervé Cauwelier <herve@itaapy.com>:
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-14 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 10:37 [PATCH 1/6] Open the pack file and keep a map on it Hervé Cauwelier
2009-10-14 10:37 ` [PATCH 2/6] Read the base offset or name of delta objects Hervé Cauwelier
2009-10-14 10:37 ` [PATCH 3/6] Allow zlib to read a pack buffer longer than the actual data Hervé Cauwelier
2009-10-14 10:37 ` [PATCH 4/6] Inflate an object from a pack file Hervé Cauwelier
2009-10-14 10:37 ` [PATCH 5/6] This assertion is valid for both loose and packed objects Hervé Cauwelier
2009-10-14 10:37 ` [PATCH 6/6] Read an object from a pack file Hervé Cauwelier
2009-10-14 12:48 ` Sverre Rabbelier [this message]
2009-10-14 15:29 ` [PATCH 1/6] Open the pack file and keep a map on it Hervé Cauwelier
2009-10-14 15:30 ` Sverre Rabbelier
-- strict thread matches above, loose matches on Subject: below --
2009-10-03 18:09 Patches for libgit2 Hervé Cauwelier
2009-10-03 18:09 ` [PATCH 1/6] Open the pack file and keep a map on it Hervé Cauwelier
2009-10-05 15:27 ` Shawn O. Pearce
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=fabb9a1e0910140548g2ad99ec4ia0f4cd4cb6fc409c@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=herve@itaapy.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;
as well as URLs for NNTP newsgroup(s).