From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Debugging strange "corrupt pack" errors on SuSE 9
Date: Wed, 20 Jun 2007 10:46:33 +0200 [thread overview]
Message-ID: <f5apha$sj7$3@sea.gmane.org> (raw)
In-Reply-To: alpine.LFD.0.99.0706192313290.20596@xanadu.home
Nicolas Pitre wrote:
> But because you push to a local repository (a mounted USB stick is
> considered a local repo) then you don't get to negociate the pack
> capabilities of the final destination, and therefore more "bad" delta
> objects might sneak in again.
So if he pushes over ssh (ssh localhost) he would get capabilities
negotiation, at the cost of being slower?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-06-20 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 2:36 Debugging strange "corrupt pack" errors on SuSE 9 Martin Langhoff
2007-06-20 3:33 ` Nicolas Pitre
2007-06-20 4:17 ` Martin Langhoff
2007-06-20 4:20 ` Martin Langhoff
2007-06-20 5:14 ` Nicolas Pitre
2007-06-20 5:01 ` Nicolas Pitre
2007-06-20 5:10 ` Martin Langhoff
2007-06-20 5:17 ` Nicolas Pitre
2007-06-20 5:12 ` Nicolas Pitre
2007-06-20 8:46 ` Jakub Narebski [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='f5apha$sj7$3@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).