Commits on Source 5

  • Angelos Evripiotis's avatar
    news: fix 'osbolete' spelling · 5df4105a
    Angelos Evripiotis authored
    5df4105a
  • Angelos Evripiotis's avatar
    Fixup refs to 'bst track' · 9c981eff
    Angelos Evripiotis authored
    Now that 'bst track' is obsolete, change guidance to refer to the
    replacement 'bst source track' instead.
    9c981eff
  • Angelos Evripiotis's avatar
    Fixup refs to 'bst fetch' · bef80291
    Angelos Evripiotis authored
    Now that 'bst fetch' is obsolete, change guidance to refer to the
    replacement 'bst source fetch' instead.
    bef80291
  • Angelos Evripiotis's avatar
    Merge branch 'aevri/bst_track_guidance' into 'master' · 564cb245
    Angelos Evripiotis authored
    Fixup refs to 'bst track' and 'bst fetch'
    
    See merge request !1086
    564cb245
  • Angelos Evripiotis's avatar
    BREAK:remove unconditional 'are you sure?' prompts · bfcc5281
    Angelos Evripiotis authored
    This is a breaking change, as it affects behaviour that people might be
    relying on. An entry has been added to NEWS.
    
    As proposed on the mailing list, this change removes the unconditional
    prompts on:
    
        o: bst workspace reset
        o: bst workspace close --remove-dir
    
    If interactive, these commands would always interrupt you with a prompt
    like this:
    
        This will remove all your changes, are you sure?
    
    This seems like it may just save someone's work some time. It may also
    condition folks to hit 'y' quickly without thinking.
    
    This change also makes the non-interactive behaviour consistent with the
    interactive behaviour in the default case. There is also the case of the
    prompt configured by 'really-workspace-close-project-inaccessible',
    which may be tackled in later work.
    
    This change also removes the new config options to suppress those
    prompts, and their associated news entry.
    
    The relevant bit of the mailing list conversation is here:
    https://mail.gnome.org/archives/buildstream-list/2018-December/msg00106.html
    
    The issue to make interactive and non-interactive behaviour consistent
    is here:
    #744
    bfcc5281
Loading
Loading