From: "mail@samtuke.com" <mail@samtuke.com>
To: git@vger.kernel.org
Subject: Adding non-bare branches to a non-bare repository
Date: Thu, 3 Mar 2011 10:53:35 +0000 [thread overview]
Message-ID: <201103031053.35864.mail@samtuke.com> (raw)
Hi,
My website is a non-bare git repository. I have a copy of the website for
testing purposes which is a separate git repository. Currently these two
repositories are not aware of each other, and I copy across files from one to
the other in order to bring features from the test repo into the live site.
I would like to make the testing repository into a branch of the live website
repository so that I can easily merge in changes from one to the other.
Both repositories need to be complete copies of files as they are web
accessible and must be functional.
Is this possible?
In future I also need to make a third copy of the site to have a beta as well
as an alpha testing copy of the website.
Thanks,
Sam.
next reply other threads:[~2011-03-03 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 10:53 mail [this message]
2011-03-03 14:23 ` Adding non-bare branches to a non-bare repository Michael J Gruber
2011-03-06 23:23 ` Neal Kreitzinger
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=201103031053.35864.mail@samtuke.com \
--to=mail@samtuke.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).