Home
last modified time | relevance | path

Searched refs:branch (Results 1 – 25 of 54) sorted by relevance

123

/f-stack/freebsd/contrib/device-tree/scripts/
H A Dcronjob37 for branch in $BRANCHES ; do
38 REF=$(git show-ref --verify refs/heads/${branch})
40 echo "Tree is missing required branch ${branch}, aborting" 1>&2
115 git branch -D "${TESTBRANCH}"
118 for branch in ${BRANCHES} ; do
119 REF=$(git show-ref --verify refs/heads/${branch})
H A Dfilter.sh30 git branch -f $UPSTREAM_REWRITTEN FETCH_HEAD
32 git filter-branch --force \
37 --prune-empty --state-branch refs/heads/filter-state \
40 git branch -f $UPSTREAM_MASTER FETCH_HEAD
/f-stack/freebsd/arm/arm/
H A Ddisassem.c295 int branch; in disasm() local
401 branch = ((insn << 2) & 0x03ffffff); in disasm()
402 if (branch & 0x02000000) in disasm()
403 branch |= 0xfc000000; in disasm()
404 di->di_printaddr(loc + 8 + branch); in disasm()
408 branch = ((insn << 2) & 0x03ffffff) | in disasm()
410 if (branch & 0x02000000) in disasm()
411 branch |= 0xfc000000; in disasm()
412 di->di_printaddr(loc + 8 + branch); in disasm()
/f-stack/freebsd/contrib/zstd/
H A DTESTING.md9 Short tests run on CircleCI for new commits on every branch and pull request.
18 Medium tests run on every commit and pull request to `dev` branch, on TravisCI.
30 Long tests run on all commits to `release` branch,
31 and once a day on the current version of `dev` branch,
H A DCONTRIBUTING.md6 New versions are being developed in the "dev" branch,
7 or in their own feature branch.
11 or their own feature branch.
16 1. Fork the repo and create your branch from `dev`.
32 related changes into a branch.
42 * Update your local dev branch
51 git checkout -b <branch-name>
52 git push origin <branch-name>
58 git push origin <branch-name>
79 … * From there, select the branch where you made changes as your source branch and facebook:dev
[all …]
H A DREADME.md12 **Development branch status:**
20 [travisDevBadge]: https://travis-ci.org/facebook/zstd.svg?branch=dev "Continuous Integration test s…
22 [AppveyorDevBadge]: https://ci.appveyor.com/api/projects/status/xt38wbdxjk5mrbem/branch/dev?svg=tru…
26 [CirrusDevBadge]: https://api.cirrus-ci.com/github/facebook/zstd.svg?branch=dev
196 The `dev` branch is the one where all contributions are merged before reaching `release`.
197 If you plan to propose a patch, please commit into the `dev` branch, or its own feature branch.
H A Dappveyor.yml1 # Following tests are run _only_ on `release` branch
2 # and on selected feature branch named `appveyorTest` or `visual*`
81 sh -c "cd .. && git clone --depth 1 --branch v1.2.11 https://github.com/madler/zlib" &&
95 git clone --depth 1 --branch release https://github.com/facebook/zstd &&
186 # into `dev` or some feature branch
/f-stack/freebsd/contrib/device-tree/Bindings/clock/
H A Dlpc1850-ccu.txt5 branch clocks are distributed between CCU1 and CCU2.
20 are the branch clock names defined in table below.
35 Which branch clocks that are available on the CCU depends on the
H A Dqcom,sdm845-gpucc.yaml25 - description: GPLL0 main branch source
26 - description: GPLL0 div branch source
H A Dqcom,sc7180-gpucc.yaml25 - description: GPLL0 main branch source
26 - description: GPLL0 div branch source
H A Dqcom,gpucc.yaml33 - description: GPLL0 main branch source
34 - description: GPLL0 div branch source
H A Dqcom,msm8998-gpucc.yaml25 - description: GPLL0 main branch source (gcc_gpu_gpll0_clk_src)
/f-stack/dpdk/doc/guides/contributing/
H A Dstable.rst38 longer, up to 1 year, if a maintainer continues to support the stable branch,
54 After the X.11 release, an LTS branch will be created for it at
70 point the LTS branch will no longer be maintained with no further releases.
77 branch with a Fixes: tag should be backported to the relevant stable/LTS
111 All fix patches to the main branch that are candidates for backporting
/f-stack/app/redis-5.0.5/utils/
H A Dspeed-regression.tcl77 foreach {branch output} $results {
79 $branch [get-result-with-name $output $test]]
/f-stack/freebsd/contrib/libsodium/
H A DREADME.markdown1 …https://travis-ci.org/jedisct1/libsodium.svg?branch=master)](https://travis-ci.org/jedisct1/libsod…
/f-stack/app/redis-5.0.5/utils/releasetools/
H A Dchangelog.tcl8 set branch [lindex $::argv 0]
/f-stack/
H A D.code.yml1 branch:
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dvm_power_management.rst47 branch miss/hit ratio. See :ref:`enabling_out_of_band`.
129 doing this is to monitor the ratio of the branch miss to branch hits
132 branch misses to branch hits is very low, but when the core is
407 monitoring of branch ratios on cores doing busy polling using PMDs as
410 ``--core-branch-ratio {list of cores}:{branch ratio for listed cores}``
411 Specify the list of cores to monitor the ratio of branch misses
412 to branch hits. A tightly-polling PMD thread has a very low
413 branch ratio, therefore the core frequency scales down to the
415 causing the branch ratio to increase. When the ratio goes above
423 The branch ratio mechanism can also be useful for non-PMD cores and
[all …]
/f-stack/app/redis-5.0.5/
H A DCONTRIBUTING36 b. Create a topic branch (git checkout -b my_branch)
37 c. Push to your branch (git push origin my_branch)
/f-stack/app/redis-5.0.5/utils/graphs/commits-over-time/
H A DREADME.md14 Note that the code filtering the tags, and the hardcoded branch name, does
/f-stack/dpdk/examples/vm_power_manager/
H A Dmeson.build33 # If we're on X86, pull in the x86 code for the branch monitor algo.
/f-stack/dpdk/devtools/
H A Dgit-log-fixes.sh47 git branch $refbranch --contains $t |
/f-stack/freebsd/contrib/libsodium/src/libsodium/sodium/
H A Dcore.c30 # warning Alternatively, use the "stable" branch in the git repository.
/f-stack/freebsd/contrib/openzfs/
H A DREADME.md7 [![codecov](https://codecov.io/gh/openzfs/zfs/branch/master/graph/badge.svg)](https://codecov.io/gh…
/f-stack/freebsd/mips/nlm/
H A Dfiles.xlp26 …unroll-loops -fomit-frame-pointer -Wno-unused-command-line-argument -mno-branch-likely -fno-pic -m…

123