The Tor Browser / file comparison
comparison: CLOBBER
CLOBBER
- branch
- TOR_BUG_9701
- changeset 8
- 97036ab72558
equal
deleted
inserted
replaced
| -1:000000000000 | 0:367965c6ff98 |
|---|---|
| 1 # To Trigger a clobber replace ALL of the textual description below, | |
| 2 # giving a bug number and a one line description of why a clobber is | |
| 3 # required. Modifying this file will make configure check that a | |
| 4 # clobber has been performed before the build can continue. | |
| 5 # | |
| 6 # MERGE NOTE: When merging two branches that require a CLOBBER, you should | |
| 7 # merge both CLOBBER descriptions, to ensure that users on | |
| 8 # both branches correctly see the clobber warning. | |
| 9 # | |
| 10 # O <-- Users coming from both parents need to Clobber | |
| 11 # / \ | |
| 12 # O O | |
| 13 # | | | |
| 14 # O <-- Clobber O <-- Clobber | |
| 15 # | |
| 16 # Note: The description below will be part of the error message shown to users. | |
| 17 # | |
| 18 # Modifying this file will now automatically clobber the buildbot machines \o/ | |
| 19 # | |
| 20 | |
| 21 # Are you updating CLOBBER because you think it's needed for your WebIDL | |
| 22 # changes to stick? As of bug 928195, this shouldn't be necessary! Please | |
| 23 # don't change CLOBBER for WebIDL changes any more. | |
| 24 | |
| 25 Merge day clobber |
