• Home
    • View
    • Login
    This page
    • Normal
    • Export PDF
    • Page Information

    Loading...
  1. Dashboard
  2. Undefined Space
  3. Build
  4. Submission Forests

Page History

Versions Compared

Old Version 20

changes.mady.by.user Brian Beck

Saved on Oct 18, 2016

compared with

New Version 21

changes.mady.by.user Brian Beck

Saved on Oct 18, 2016

  • Previous Change: Difference between versions 19 and 20
  • Next Change: Difference between versions 21 and 22
  • View Page History

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Changes from the upstream forest are pulled into the submission forest automatically.  You can keep your work on a fix branch in sync with what's going on upstream by simply merging in changes from the default branch.

Is jcheck

...

turned on?

Jcheck is not enabled for the submission forest; however, it generally is enabled for the upstream forest.  If so, your change must pass jcheck when it is merged with the upstream forest.

...

Once your branch has been integrated upstream, it will be closed automatically be closed..  This is the common case.  Occasionally though, there may be a branch that needs to be abandoned.  This might happen when a branch has been pushed to the submission forest but  failed to integrate upstream. 

 

Can I reuse a branch for a different fix?

...

Overview
Content Tools
ThemeBuilder

Terms of Use
• License: GPLv2
• Privacy • Trademarks • Contact Us

Powered by a free Atlassian Confluence Open Source Project License granted to https://www.atlassian.com/software/views/opensource-community-additional-license-offer. Evaluate Confluence today.

  • Kolekti ThemeBuilder Powered by Atlassian Confluence 8.5.21
  • Kolekti ThemeBuilder printed.by.atlassian.confluence
  • Report a bug
  • Atlassian News
Atlassian
Kolekti ThemeBuilder EngineAtlassian Confluence
{"serverDuration": 405, "requestCorrelationId": "0305f8720dc72ba1"}