From: Matthias Kestenholz <lists@irregular•ch>
To: Andreas Ericsson <ae@op5•se>
Cc: git@vger•kernel.org
Subject: Re: Bug encountered while comitting
Date: Sat, 25 Mar 2006 02:15:30 +0100 [thread overview]
Message-ID: <20060325011530.GA25951@spinlock.ch> (raw)
In-Reply-To: <442449E1.5060007@op5.se>
* Andreas Ericsson (ae@op5•se) wrote:
> Matthias Kestenholz wrote:
> >
> >The PHP script created directories under .git/objects
>
>
> Ouch... You're not really supposed to do that. The proper thing to do is
> to do things in the working tree and commit them to git later.
>
I think I did not express myself clearly. The PHP Script executes
git commands which in turn create or modify the mentioned
directories. I do not create them myself by hand.
> >When I tried to commit, I got a message saying "Unable to write sha1
> >filename".
> >
>
> What file were you trying to write?
>
Some file I was updating (in this case, a file holding some wiki
content)
> >The result was, that only part of the commit was recorded and that I
> >experienced repository corruption. refs/heads/master pointed to a
> >non-existant object.
> >
>
> Did you use git tools to update .git/refs/heads/master ?
>
Yes.
>
> >The expected behavior would have been an error message telling me I
> >had insufficient write privileges and surely no repository
> >corruption.
> >
>
> Didn't you get the strerror(3) message from that? If so, I'd consider it
> a bug.
As I (only now) wrote in the other email, I got the
"Permission denied" message, and that was a sufficient hint what was
wrong.
--
:wq
next prev parent reply other threads:[~2006-03-25 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 18:39 Bug encountered while comitting Matthias Kestenholz
2006-03-24 19:34 ` Andreas Ericsson
2006-03-25 1:15 ` Matthias Kestenholz [this message]
2006-03-24 22:55 ` Junio C Hamano
2006-03-25 1:15 ` Matthias Kestenholz
2006-03-25 6:17 ` Junio C Hamano
2006-03-25 10:23 ` Matthias Kestenholz
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=20060325011530.GA25951@spinlock.ch \
--to=lists@irregular$(echo .)ch \
--cc=ae@op5$(echo .)se \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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