DWT repository moved to github

Jacob Carlborg doob at me.com
Thu Jan 12 04:04:02 PST 2012


On 2012-01-12 12:09, kntroh wrote:
> == Quote from Jacob Carlborg (doob at 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 --init
> It failed. Submodules didn't become latest version.

git submodules refers to a specific commit and I haven't updated the 
submodules to the latest version. If you take a look at the dwt 
repository at github you can see a hash next to the name of the 
submodules. That hash refers to the commit in the repository the 
submoule points to.

I guess the reason for this is because an update of a repository that is 
a submodule shouldn't be able to break the repository that includes the 
submodule.

So in this case the dwt repository decides which commits the submodules 
should refer to.

> Then I tried this command.
>> git submodule foreach git pull origin master
> It was successful. I builded my application with DWT.
> That's ok.
> But, is it right command?

No it isn't.

-- 
/Jacob Carlborg


More information about the Digitalmars-d-dwt mailing list