• 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 39

changes.mady.by.user Brian Beck

Saved on Dec 05, 2016

compared with

New Version 40

changes.mady.by.user Brian Beck

Saved on Dec 05, 2016

  • Previous Change: Difference between versions 38 and 39
  • Next Change: Difference between versions 40 and 41
  • View Page History

Key

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

...

Once your branch has been integrated upstream, it will be closed automatically.  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.  Let's say you have a branch "JDK-7000001" in the jdk repo repository that needs to be closed.  You could do the following:

Code Block
languagebash
$ # From the root of your thelocal forest
$ hg -R jdk update -C "JDK-7000001"
$ hg -R jdk commit --close-branch -m "Abandoning changes."
$ # Update repo to another branch to avoid mistakenly re-opening the closed branch.
$ hg -R jdk update default 

...

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": 223, "requestCorrelationId": "f2bf923051792cb8"}