Re: make fails on MacOS 10.13.4 with c++11 related issues

Kaganski Mike <mikekaganski -AT- hotmail.com>
Mon, 2 Apr 2018 07:34:02 +0000

On 4/2/2018 5:44 AM, Ch g wrote:

Regarding your reply:To purge all modifications do "git fetch --all && 
git reset --hard origin/master".


will "git reset --hard origin/master" undo changes already made in 
custom branches?


You could send your branches to gerrit as drafts to ensure safety, then 
reset your tree, then recreate branches and cherry-pick the drafts from 
gerrit back.


-- 
Best regards,
Mike Kaganski

Context

autogen.sh fails on MacOS 10.13.3 · Ch g
- Re: autogen.sh fails on MacOS 10.13.3 · Heiko Tietze
  - (message not available)
    - (message not available)
      - Fwd: MacOSX10.13.sdk has broken static initializer_list support · Tor Lillqvist
  - make fails on MacOS 10.13.4 with c++11 related issues · Ch g
    - Re: make fails on MacOS 10.13.4 with c++11 related issues · Noel Grandin
      - Re: make fails on MacOS 10.13.4 with c++11 related issues · Ch g
        
        Re: make fails on MacOS 10.13.4 with c++11 related issues · Tor Lillqvist
        
        Re: make fails on MacOS 10.13.4 with c++11 related issues · Ch g
    - Re: make fails on MacOS 10.13.4 with c++11 related issues · Heiko Tietze
    - Re: make fails on MacOS 10.13.4 with c++11 related issues · Kaganski Mike
      - Re: make fails on MacOS 10.13.4 with c++11 related issues · Thorsten Behrens
- Re: autogen.sh fails on MacOS 10.13.3 · Tor Lillqvist

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.