From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: [JGIT PATCH 0/3] Improved object validation
Date: Thu, 30 Oct 2008 10:46:22 -0700 [thread overview]
Message-ID: <1225388785-26818-1-git-send-email-spearce@spearce.org> (raw)
This is mostly a resend as I haven't heard anything on the series.
One new patch at the end, to handle '.' and '..' cases.
Shawn O. Pearce (3):
Check object connectivity during fetch if fsck is enabled
Add --[no-]thin and --[no-]fsck optiosn to fetch command line tool
Don't permit '.' or '..' in tree entries
.../src/org/spearce/jgit/pgm/Fetch.java | 20 +++++++++++++
.../org/spearce/jgit/lib/ObjectCheckerTest.java | 31 ++++++++++++++++++++
.../src/org/spearce/jgit/lib/ObjectChecker.java | 7 ++++
.../jgit/transport/BasePackFetchConnection.java | 4 ++
.../spearce/jgit/transport/FetchConnection.java | 22 ++++++++++++++
.../org/spearce/jgit/transport/FetchProcess.java | 13 +++++++-
.../spearce/jgit/transport/TransportBundle.java | 4 ++
.../jgit/transport/WalkFetchConnection.java | 4 ++
8 files changed, 103 insertions(+), 2 deletions(-)
next reply other threads:[~2008-10-30 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 17:46 Shawn O. Pearce [this message]
2008-10-30 17:46 ` [JGIT PATCH 1/3] Check object connectivity during fetch if fsck is enabled Shawn O. Pearce
2008-10-30 17:46 ` [JGIT PATCH 2/3] Add --[no-]thin and --[no-]fsck optiosn to fetch command line tool Shawn O. Pearce
2008-10-30 17:46 ` [JGIT PATCH 3/3] Don't permit '.' or '..' in tree entries Shawn O. Pearce
2008-10-31 0:01 ` [JGIT PATCH 0/3] Improved object validation Robin Rosenberg
2008-10-31 14:55 ` 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=1225388785-26818-1-git-send-email-spearce@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.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).