On Feb 15, 4:16 am, Daniel Trezub wrote:
> Ok, thanks. So, even if my remote repo is a brand-new one and my local repo
> is ages old with a lots of history, after the push the remote repo will have
> all my history?
If all your history is reachable from the branch head that you're
pushing to th
Ok, thanks. So, even if my remote repo is a brand-new one and my local repo
is ages old with a lots of history, after the push the remote repo will have
all my history?
=
Daniel Trezub
http://www.gameblogs.com.br
On 13 February 2011 23:46, Jeenu wrote:
>
>
> On Feb 14, 5:15 am, Daniel Trez
On Feb 14, 5:15 am, Daniel Trezub wrote:
> It's always good to have your release/master branch to have a linear
>
> > history.
>
> Why? Does it make things easier when pushing to the remote repo?
It's got nothing to do with pushing. It's just that your graph will
look tidy and it'll more readab
Hi, guys.
Some other questions:
It depends a bit on what you already have on your live site.
>
Why? My live site is supposed to be the same version from my master branch
in my local repo.
4) Clear out the live server (or move the old contents away or something)
>
But this way I'll have a downt
On Feb 12, 6:40 am, Daniel Trezub wrote:
> Hi,
>
> I've been working with git in my local repo for some months already (i.e.
> there is already a bunch of commits and some branches), and I'd like to use
> git to integrate with my online server (use git pull, push, clone, fetch,
> etc).
>
> How s
It depends a bit on what you already have on your live site.
I think you should make a distinction between working on the source code
using git repositories, and doing actual deployment of your site.
I think I would do something like this. First you want to set up a
reproducable/scriptable rout
