From: Christian Couder <christian.couder@gmail.com>
To: Rossella Barletta <rossella.barletta@gmail.com>
Cc: Philip Oakley <philipoakley@iee.org>, git <git@vger.kernel.org>,
"dario.ligorio" <dario.ligorio@selex-es.com>
Subject: Re: Permission denied ONLY after pulling bundles
Date: Fri, 5 Jun 2015 18:01:14 +0200 [thread overview]
Message-ID: <CAP8UFD0gMCnaJnXNxe6Tmwxes7c4Wqgga1d8AzSNEcFxtHtGWg@mail.gmail.com> (raw)
In-Reply-To: <CAJeiYQH9jF4S6FivHW5xc_xeef5kL1r1xF+yjJuHf7Wa0yUifw@mail.gmail.com>
On Fri, Jun 5, 2015 at 8:54 AM, Rossella Barletta
<rossella.barletta@gmail.com> wrote:
[...]
> FIST ONE (PERMISSION PROBLEMS)
>
> - Repo is on windows
> - Repo folder is shared
> -Repo is a copy of another repository being on a machine in another
> city on which we cannot access. We got all the files, included the
> folder .git a put everything in our shared folder
> - Mounted the Repo folder on Linux
> -Created the clone
> - got a bundle from the original repository (bundle created from a branch)
> -pulled the bundle in the same branch
>
>
>
> SECOND ONE (NO PROBLEMS BUT WE CANT USE THIS)
> - Repo is on Linux
> -Repo is a copy of another repository being on a machine in another
> city on which we cannot access.
> - got a bundle from the original repository (bundle created from a branch)
> -pulled the bundle in the same branch
>
>
>
> 4) Git version is 1.7.1
It would be nice if you could try to reproduce the problem:
- using a recent Git, as v1.7.1 is 5 years old,
- using a small fake repo,
- doing everything on Windows.
Best,
Christian.
next prev parent reply other threads:[~2015-06-05 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 13:04 Permission denied ONLY after pulling bundles Rossella Barletta
2015-06-04 19:06 ` Christian Couder
2015-06-04 19:25 ` Philip Oakley
2015-06-05 6:54 ` Rossella Barletta
2015-06-05 16:01 ` Christian Couder [this message]
2015-06-08 8:34 ` Rossella Barletta
2015-06-08 8:47 ` Rossella Barletta
2015-06-08 13:03 ` Thomas Ferris Nicolaisen
2015-06-08 15:19 ` Rossella Barletta
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=CAP8UFD0gMCnaJnXNxe6Tmwxes7c4Wqgga1d8AzSNEcFxtHtGWg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=dario.ligorio@selex-es.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
--cc=rossella.barletta@gmail.com \
/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).