From: Michael J Gruber <git@drmicha.warpmail.net>
To: "mail@samtuke.com" <mail@samtuke.com>
Cc: git@vger.kernel.org
Subject: Re: Adding non-bare branches to a non-bare repository
Date: Thu, 03 Mar 2011 15:23:33 +0100 [thread overview]
Message-ID: <4D6FA465.2060703@drmicha.warpmail.net> (raw)
In-Reply-To: <201103031053.35864.mail@samtuke.com>
mail@samtuke.com venit, vidit, dixit 03.03.2011 11:53:
> 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.
You probably should replace "branch" by "clone" in all that you have
said above.
There is no problem adding a non-bare repo as a new remote to an
existing non-bare repo. You can easily fetch from such a repo. The only
problematic thing is pushing to a branch in a remote repo which is
checked out there.
Michael
next prev parent reply other threads:[~2011-03-03 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 10:53 Adding non-bare branches to a non-bare repository mail
2011-03-03 14:23 ` Michael J Gruber [this message]
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=4D6FA465.2060703@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=mail@samtuke.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.