On 2012-01-12 14:29, kntroh wrote:
== Quote from Jacob Carlborg (d...@me.com)'s article
When you run "git pull" in a submodule it will grab the latest version
from the origin in the repository and the submodule will now refer to
that commit instead.
I understand.
I ran "git pull" on each submo
== Quote from Jacob Carlborg (d...@me.com)'s article
> When you run "git pull" in a submodule it will grab the latest version
> from the origin in the repository and the submodule will now refer to
> that commit instead.
I understand.
I ran "git pull" on each submodule (base, win32),
and checked t
On 2012-01-12 12:09, kntroh wrote:
== Quote from Jacob Carlborg (d...@me.com)'s article
I've merged your commits now. It says that you are the author and I am
the committer, I hope that's ok. You can now merge from upstream to get
the latest changes.
I cloned DWT from github. Then I ran this c
On 2012-01-12 12:09, kntroh wrote:
== Quote from Jacob Carlborg (d...@me.com)'s article
I've merged your commits now. It says that you are the author and I am
the committer, I hope that's ok. You can now merge from upstream to get
the latest changes.
I cloned DWT from github. Then I ran this c
== Quote from Jacob Carlborg (d...@me.com)'s article
> I've merged your commits now. It says that you are the author and I am
> the committer, I hope that's ok. You can now merge from upstream to get
> the latest changes.
I cloned DWT from github. Then I ran this command.
> git submodule update --
