From: Christian <crich-ml@beronet.com>
To: git@vger.kernel.org
Subject: git push over http is very dangerous
Date: Mon, 16 Apr 2007 17:22:20 +0200 [thread overview]
Message-ID: <462394AC.303@beronet.com> (raw)
Hi Git developers,
first of all thanks for the great toolkit :)
We are using git for the mISDN Open Source ISDN Stack (www.misdn.org /
git.misdn.org). We are using webdav to push up data from users with
write access. Readonly access is granted via the git daemon.
We have moved from CVS to git in the beginning of last week, all went
well until this weekend. This weekend one developer wanted to push some
of his local modifications, unfortunately during the push his http
connection seemed to have broken or so. Unfortunately git does not prove
if the push went well. Therefore our repository was broken this morning.
We found out that it was broken, because we could not do a pull or clone
from the central repository anymore, but we got an error message.
Then i did a "git log" which worked well. then i wanted to "show" the
last 2 commits, so i did: "git show":
error: corrupt loose object 'cd1aac1a43cfdac07118240f75c0ba7662eb8140'
<crich1999> error: cd1aac1a43cfdac07118240f75c0ba7662eb8140: object
corrupt or missing
i found that i could "git show" all commits, but only the last 2
produced the above error message.
gitster from IRC helped me out and showed me that i could do
git branch -f master master~2
to remove the 2 commits. i did that and all worked well again!
I wonder if it would be possible to delay a central push until all data
was uploaded, then after the upload finished a checksum is transmitted,
if the checksum is correct, the push can be done centrally..
cheers,
christian
next reply other threads:[~2007-04-16 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 15:22 Christian [this message]
2007-04-16 19:38 ` git push over http is very dangerous Linus Torvalds
2007-04-16 19:55 ` Junio C Hamano
2007-04-16 20:20 ` Linus Torvalds
2007-04-20 18:37 ` Christian
2007-04-21 1:03 ` Junio C Hamano
2007-04-21 17:07 ` Christian
2007-04-21 18:28 ` Junio C Hamano
2007-04-22 7:21 ` Christian
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=462394AC.303@beronet.com \
--to=crich-ml@beronet.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).