git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florent Thoumie <flz@xbsd.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Problem with git-push
Date: Wed, 01 Nov 2006 19:57:15 +0000	[thread overview]
Message-ID: <1162411035.93716.14.camel@localhost> (raw)
In-Reply-To: <7v64e0qclo.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

On Tue, 2006-10-31 at 15:39 -0800, Junio C Hamano wrote:

> A quick workaround until we sort this out would be:
> 
>  - make sure all your developers have umask suitable for group
>    work (i.e. second octal-digit from the right should be zero
>    to give group members the same rights as you do).
> 
>  - run "chmod g+w .git/objects/??" in the shared repository.

I thought I checked on the remote (guess I only looked at my local
repo), but that was it, wrong perms.

Sorry if this is a dumb question but assuming i did 3 successive
git-push's, why is the object name changing from a try to another?

Thanks for the answer.

Florent


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

      parent reply	other threads:[~2006-11-01 18:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 14:48 Problem with git-push Florent Thoumie
2006-10-31 23:39 ` Junio C Hamano
2006-11-01 11:12   ` Johannes Schindelin
2006-11-01 15:33     ` Junio C Hamano
2006-11-01 21:43       ` Junio C Hamano
2006-11-01 22:54         ` Florent Thoumie
2006-11-01 22:11           ` Junio C Hamano
2006-11-02  9:42         ` Johannes Schindelin
2006-11-01 16:21     ` Junio C Hamano
2006-11-02  9:29       ` Johannes Schindelin
2006-11-03  2:40         ` Junio C Hamano
2006-11-01 19:57   ` Florent Thoumie [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=1162411035.93716.14.camel@localhost \
    --to=flz@xbsd.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).