This did it! For a simple setup I think this works great, maybe these
instructions should go in the docs somewhere?
Thanks for your help.
On Monday, August 19, 2013 1:30:57 PM UTC-4, Jim Toth wrote:
>
> Hmm...you might need to add "git remote update" in there. git pull does
> that by defa
Hmm...you might need to add "git remote update" in there. git pull does
that by default.
On Mon, Aug 19, 2013 at 1:22 PM, me 1 wrote:
>
> On Sun, Aug 18, 2013 at 9:04 PM, me 1 wrote:
>>
>>> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
There are a few ways to go; pro
> On Sun, Aug 18, 2013 at 9:04 PM, me 1 >wrote:
>
>> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>>
>>> There are a few ways to go; probably the best way is to set up a bare
>>> repository that you push and pull from in both places, but I'd probably add
>>> the development env
On Sun, Aug 18, 2013 at 9:04 PM, me 1 >wrote:
> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>>
>>> There are a few ways to go; probably the best way is to set up a bare
>>> repository that you push and pull from in both places, but I'd probably add
>>> the development environme
> On Sun, Aug 18, 2013 at 9:04 PM, me 1 >wrote:
>
>> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>>
>>> There are a few ways to go; probably the best way is to set up a bare
>>> repository that you push and pull from in both places, but I'd probably add
>>> the development env
On Sun, Aug 18, 2013 at 9:04 PM, me 1 wrote:
> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>
>> There are a few ways to go; probably the best way is to set up a bare
>> repository that you push and pull from in both places, but I'd probably add
>> the development environment as
On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>
> There are a few ways to go; probably the best way is to set up a bare
> repository that you push and pull from in both places, but I'd probably add
> the development environment as a remote in the in-production directory.
>
> cd /pa
There are a few ways to go; probably the best way is to set up a bare
repository that you push and pull from in both places, but I'd probably add
the development environment as a remote in the in-production directory.
cd /path/to/production/repository
git remote add devel /path/to/development/dire
On Sunday, August 18, 2013 3:24:40 AM UTC-4, James Polley wrote:
>
> The changes are being commited in the branch called "master" in your local
> checkout, but not being pushed nack up to the origin.
>
> http://git-scm.com/book/en/Git-Basics-Working-with-Remotes explains how
> to push your change
Git push?
On Aug 18, 2013 1:01 AM, "me 1" wrote:
> I have created a git clone and have been using this to test changes
> without affecting the modules in production. The problem is, when I commit
> the change it stays in the closed branch, never pushing the change to the
> master (origin) branch
The changes are being commited in the branch called "master" in your local
checkout, but not being pushed nack up to the origin.
http://git-scm.com/book/en/Git-Basics-Working-with-Remotes explains how to
push your changes.
--
You received this message because you are subscribed to the Google Gro
On 08/18/2013 02:01 AM, me 1 wrote:
I have created a git clone and have been using this to test changes without
affecting the modules in production. The problem is, when I commit the
change it stays in the closed branch, never pushing the change to the
master (origin) branch. How can this be do
I have created a git clone and have been using this to test changes without
affecting the modules in production. The problem is, when I commit the
change it stays in the closed branch, never pushing the change to the
master (origin) branch. How can this be done?
$ git status
# On branch maste
13 matches
Mail list logo
