Ahh. Didn't realise that. Too used to TFS...
On 22 July 2013 13:50, Joe Alam <[email protected]> wrote:
> Hi,
>
> From what you've said it sounds like you've commited the changes to the
> local (I.E. on your machine) repository, but not pushed them to the GitHub
> repository.
>
> I've never used TortoiseGit, but in Git Bash the command you need would be
> something like "git push origin"
>
> Regards,
> Joe
>
> Please excuse typos/formatting, this email was sent using my mobile.
> On 22 Jul 2013 13:43, "Graham Reeds" <[email protected]> wrote:
>
>> I am wondering if anyone can help me out here. I am a git noob so I
>> might be doing something wrong.
>>
>> I forked the unittest++ code to here
>> https://github.com/grahamreeds/unittest-cpp.
>>
>> I checked it out using TortoiseGit, modified it, and then checked it back
>> in. All the red x on the folders in the shell are now green ticks, but the
>> updates aren't showing when I do a test pull or when I browser the folder
>> online.
>>
>> Why aren't my edits displaying in GitHub?
>>
>> Or does it take a while for checkins to show up?
>>
>> Thanks, GR
>>
>>
>> On 19 July 2013 14:18, Graham Reeds <[email protected]> wrote:
>>
>>> >> Speaking of which I was going to rename the vs projects directory to
>>> just projects and move the mac into there too.
>>> >
>>> > That would be fine, the choice to separate them was somewhat
>>> arbitrary.
>>>
>>> And my decision to move them is also arbitrary.
>>>
>>> >>
>>> >> Final change is to rename the UnitTest++ directory to src.
>>> >
>>> > The change from src to UnitTest++ was done as part of addressing an
>>> earlier issue. What issue does changing it back address?
>>>
>>> It offends my sensibilities:-)
>>>
>>> What earlier issue was there?
>>>
>>> I will also do a nicer version of the money example as that is very
>>> scrappy and doesn't exactly promote best practices.
>>>
>>> Also the tests don't run after a successful build.
>>> So far my current changes are
>>> - renamed UnitTest++ to src
>>> - renamed vs_projects to projects
>>> - moved xcode4-6 to projects
>>> - deleted folder xcode_projects
>>> - removed MinSizeRel and RelWithDebInfo from Project Configurations
>>> - removed hard-coding of paths back to how the original was
>>> - readded post-build event to TestUnitTest++
>>>
>>> GR
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> unittest-cpp-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
>>
>>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> unittest-cpp-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
unittest-cpp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
