From: Martin Fick <mfick@codeaurora.org>
To: John Ajah <john@spinlet.com>, git@vger.kernel.org
Subject: Re: GIT admin access
Date: Thu, 23 Jun 2016 12:57:06 -0600 [thread overview]
Message-ID: <4246181.WMWZBxU0cj@mfick1-lnx> (raw)
In-Reply-To: <CAMoxcSXTVUBAECoNk0ePzWLZ2ShRXz5uZ8mHNgEcu0FqZMADSg@mail.gmail.com>
Brigning this back on list so that someone else can help...
On Thursday, June 23, 2016 05:01:18 PM John Ajah wrote:
> I'm on a private git, installed on a work server. Now the
> guy who set it up is not available and I want to give
> access to someone working for me, but I don't know how to
> do that.
I don't know what type of setup a "private git" means? Is
this a machine with ssh access, is it git-daemon, git-hub,
git-olite, gerrit, ...?
> This is the error the developer got when he tried cloning:
>
> FATAL ERROR: Network error: Connection timed out
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> My partner wants to set up another Git server and transfer
> our content to the new server from the one we're
> currently using. I think this is very risky and I also
> think there has to be a way to provide access without
> doing this.
We need to know what product you are running to help.
What risks are you concerned with setting up another server?
And what kind of server would you be setting up?
-Martin
--
The Qualcomm Innovation Center, Inc. is a member of Code
Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2016-06-23 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 14:43 GIT admin access john
[not found] ` <1707153.Ui0LYF9gxZ@mfick1-lnx>
[not found] ` <CAMoxcSXTVUBAECoNk0ePzWLZ2ShRXz5uZ8mHNgEcu0FqZMADSg@mail.gmail.com>
2016-06-23 18:57 ` Martin Fick [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=4246181.WMWZBxU0cj@mfick1-lnx \
--to=mfick@codeaurora.org \
--cc=git@vger.kernel.org \
--cc=john@spinlet.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).