Am 08.07.2015 um 20:05 schrieb Jeff King:
We also don't write objects directly, of course; we write to a temporary
file and try to link them into place. It really sounds more like the
"objects/d9" directory is where the permission problems are. But, hmm...
Not on Windows: A read-only file canno
Le 8/07/2015 20:05, Jeff King a écrit :
On Wed, Jul 08, 2015 at 07:41:48PM +0200, Johannes Sixt wrote:
Yes, but remember that git stores all of the objects for all of the
commits. So for some reason your push is perhaps trying to send an
object that the other side already has. Usually this does
On Wed, Jul 08, 2015 at 07:41:48PM +0200, Johannes Sixt wrote:
> >Yes, but remember that git stores all of the objects for all of the
> >commits. So for some reason your push is perhaps trying to send an
> >object that the other side already has. Usually this does not happen
> >(the receiver says
Am 07.07.2015 um 21:49 schrieb Jeff King:
On Tue, Jul 07, 2015 at 09:31:25PM +0200, X H wrote:
For the moment, I'm the only one pushing to the remote, always with
the same user (second user is planned). I use git-for-windows which is
based on MSYS2. I have mounted the network share with noacl o
On Tue, Jul 7, 2015 at 3:49 PM, Jeff King wrote:
> On Tue, Jul 07, 2015 at 09:31:25PM +0200, X H wrote:
>
>> For the moment, I'm the only one pushing to the remote, always with
>> the same user (second user is planned). I use git-for-windows which is
>> based on MSYS2. I have mounted the network s
On Tue, Jul 07, 2015 at 09:31:25PM +0200, X H wrote:
> For the moment, I'm the only one pushing to the remote, always with
> the same user (second user is planned). I use git-for-windows which is
> based on MSYS2. I have mounted the network share with noacl option so
> permissions should be handle
On Tue, Jul 07, 2015 at 03:45:50PM +0200, X H wrote:
> remote: error: unable to write sha1 filename
> objects/d9/4bfb39cd0be7497e493bd4045111a7b1158134: Permission denied
> remote: fatal: failed to write object
> error: unpack failed: unpack-objects abnormal exit
It looks like the permissions of
Hi,
I have a remote repository on a network share configured as a file remote.
I have pushed the HEAD of a branch to the remote, then amend the local HEAD. I
then try to push the HEAD again but it was rejected.
I made multiple attempts and then try to force the push with: $ git push -f
origin br
8 matches
Mail list logo
