From: Drew Northup <n1xim.email@gmail.com>
To: Enrico Weigelt <enrico.weigelt@vnc.biz>
Cc: Jeff King <peff@peff.net>, git <git@vger.kernel.org>
Subject: Re: Auto-repo-repair
Date: Sun, 18 Nov 2012 11:37:57 -0500 [thread overview]
Message-ID: <CAM9Z-nn1S9JvfcymotOvSis4CoYco0Htn4uoETZn2kCto0z9zw@mail.gmail.com> (raw)
In-Reply-To: <075f74ff-cafb-4021-ba4d-2474b6fb1853@zcs>
On Sat, Nov 17, 2012 at 4:21 AM, Enrico Weigelt <enrico.weigelt@vnc.biz> wrote:
> Hi,
>
>> You can't reliably just grab the broken objects, because most
>> transports
>> don't support grabbing arbitrary objects (you can do it if you have
>> shell access to a known-good repository, but it's not automated).
>
> can we introduce a new or extend existing transports to support that ?
How would the broken repository be sure of what it is missing to
request it from the other side?
--
-Drew Northup
--------------------------------------------------------------
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
next prev parent reply other threads:[~2012-11-18 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0c0e34a4-16ab-40a0-9293-af94e34e4290@zcs>
2012-11-16 17:51 ` Auto-repo-repair Enrico Weigelt
2012-11-16 19:00 ` Auto-repo-repair Jeff King
2012-11-17 9:21 ` Auto-repo-repair Enrico Weigelt
2012-11-18 16:37 ` Drew Northup [this message]
2012-11-18 16:55 ` Auto-repo-repair Enrico Weigelt
2012-11-19 3:30 ` Auto-repo-repair Drew Northup
2012-11-19 22:35 ` Auto-repo-repair Enrico Weigelt
2012-11-20 11:56 ` Auto-repo-repair Drew Northup
2012-11-22 23:16 ` Auto-repo-repair Enrico Weigelt
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=CAM9Z-nn1S9JvfcymotOvSis4CoYco0Htn4uoETZn2kCto0z9zw@mail.gmail.com \
--to=n1xim.email@gmail.com \
--cc=enrico.weigelt@vnc.biz \
--cc=git@vger.kernel.org \
--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).