From: shyam218 <krishnah014@gmail.com>
To: git@vger.kernel.org
Subject: Migration from Github hosted git repository to local server.
Date: Sat, 15 Mar 2014 11:58:13 -0700 (PDT) [thread overview]
Message-ID: <1394909893698-7605713.post@n2.nabble.com> (raw)
Hi All,
Could some one help me on this please,we have few repositories in the Github
and out of them couple of them are using encryption with
git-encrypt(https://github.com/shadowhand/git-encrypt)using this they have
encrypted the whole repo.
Now,we got a requirement to move all those repositories to In house
server,just for preserving the source code from hosting in third party tool.
Anybody help me in migrating them with out loosing any history and i really
appreciate if some one can give a detailed steps on how to decrypt the
encrypted file(procedure mentioned in the git-encrypt wasn't helpful
(https://github.com/shadowhand/git-encrypt) and the link for decryption
mentioned in it is also not working)
Regards,
Shyam.
--
View this message in context: http://git.661346.n2.nabble.com/Migration-from-Github-hosted-git-repository-to-local-server-tp7605713.html
Sent from the git mailing list archive at Nabble.com.
reply other threads:[~2014-03-15 18:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1394909893698-7605713.post@n2.nabble.com \
--to=krishnah014@gmail.com \
--cc=git@vger.kernel.org \
/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).