Home
last modified time | relevance | path

Searched refs:rebase (Results 1 – 25 of 94) sorted by relevance

1234

/third_party/typescript/tests/baselines/reference/
DemitSkipsThisWithRestParameter.symbols2 function rebase(fn: (base: any, ...args: any[]) => any): (...args: any[]) => any {
3 >rebase : Symbol(rebase, Decl(emitSkipsThisWithRestParameter.ts, 0, 0))
DemitSkipsThisWithRestParameter.js2 function rebase(fn: (base: any, ...args: any[]) => any): (...args: any[]) => any {
10 function rebase(fn) {
DemitSkipsThisWithRestParameter.types2 function rebase(fn: (base: any, ...args: any[]) => any): (...args: any[]) => any {
3 >rebase : (fn: (base: any, ...args: any[]) => any) => (...args: any[]) => any
/third_party/mesa3d/docs/
Drepository.rst133 would rebase your branch prior to merging with main. But for small
134 changes to the main branch itself, you also need to use the rebase
166 git pull --rebase
178 If the rebase resulted in conflicts or changes that could affect the
182 If you want the rebase action to be the default action, then
186 git config branch.main.rebase true
Dsubmittingpatches.rst164 to test this is to make use of the \`git rebase\` command, to run your
170 $ git rebase --interactive --exec "meson test -C build/" origin/main
190 Tick the following when creating the MR. It allows developers to rebase
381 - ``git rebase -i ...`` is your friend. Don't be afraid to use it.
388 git rebase -i --autosquash ...
394 git rebase -i --exec="ninja -C build/" HEAD~8
/third_party/node/deps/npm/scripts/
Dpr55 git pull --rebase origin pull/$num/head
58 git rebase -i $curbranch # squash and test
/third_party/skia/docker/skia-release/
DDockerfile12 # Set fake identity for git rebase. See thread in
31 && git rebase ${HASH}; fi
/third_party/typescript/tests/cases/compiler/
DemitSkipsThisWithRestParameter.ts1 function rebase(fn: (base: any, ...args: any[]) => any): (...args: any[]) => any { function
/third_party/skia/third_party/externals/tint/tools/
Droll-all54 git rebase --interactive "${old_head}"
/third_party/skia/docker/skia-wasm-release/
DDockerfile18 # Set fake identity for git rebase. See thread in
37 && git rebase ${HASH}; fi
/third_party/spirv-tools/utils/
Droll_deps.sh46 git rebase --interactive "${old_head}"
/third_party/skia/third_party/externals/dawn/scripts/
Droll-shader-deps.sh47 git rebase --interactive "${old_head}"
/third_party/skia/third_party/externals/spirv-tools/utils/
Droll_deps.sh49 git rebase --interactive "${old_head}"
/third_party/skia/third_party/externals/swiftshader/third_party/SPIRV-Tools/utils/
Droll_deps.sh49 git rebase --interactive "${old_head}"
/third_party/ltp/doc/
Dc-test-tutorial-simple.txt285 Git-rebase, which allows us to clean up the commit history. So don't worry
801 After that we have the pleasure of doing an interactive 'rebase' to clean up
810 tutorial and 'rebase' it. You should try following along with your own
817 152d39fe7 (HEAD -> tutorial-rebase2, tutorial-rebase) tutorial: Start Submitting patch section
823 1e24a5fb5 (me/tutorial-rebase) fixup! tutorial
837 'rebase' and submitted a patch for review, so my original branch was just called
852 $ git rebase -i 5ca627b78\^
856 This begins an interactive 'rebase' where commit 5ca6427b78 is the earliest
858 commit before this one. The interactive 'rebase' command takes the last commit
867 [source,rebase]
[all …]
/third_party/gn/src/gn/
Dcommand_meta.cc70 gn meta out/Debug "//base/foo" --data=files --rebase="/"
Dfunctions_target.cc988 If `rebase` is used in the following generated_file target:
994 rebase = root_build_dir
1012 rebase
Dninja_generated_file_target_writer.cc63 target_->rebase(), /*deps_only = */ true, in GenerateFile()
/third_party/skia/third_party/externals/angle2/doc/
DCodeReviewProcess.md47 There should be no need to rebase via the "Rebase Change" button prior
56 * If this cherry pick fails, you will need to rebase the patch yourself
/third_party/flutter/skia/third_party/externals/angle2/doc/
DCodeReviewProcess.md47 There should be no need to rebase via the "Rebase Change" button prior
56 * If this cherry pick fails, you will need to rebase the patch yourself
/third_party/node/doc/guides/
Dcommit-queue.md11 the Action will rebase it and push to master.
48 …handled by the [`--autosquash`](https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt--…
Dmaintaining-npm.md44 $ git rebase --whitespace=fix master
/third_party/flutter/flutter/bin/internal/
DREADME.md11 that pull request. If it's `rebase`, the number of commits in the framework is
/third_party/ffmpeg/doc/
Dgit-howto.texi96 git pull (--rebase)
104 @command{--rebase} (see below) is recommended.
110 git pull --rebase
322 git rebase -i origin/master
329 @command{git reset}, @command{git commit --amend} and @command{git rebase}
/third_party/mesa3d/src/mesa/drivers/dri/i965/
Dbrw_misc_state.c157 bool rebase = tile_x & 7 || tile_y & 7; in rebase_depth_stencil() local
160 rebase |= (!devinfo->has_surface_tile_offset && (tile_x || tile_y)); in rebase_depth_stencil()
162 if (rebase) { in rebase_depth_stencil()

1234