Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
95a7cbb0
Commit
95a7cbb0
authored
Sep 25, 2016
by
Clément Bœsch
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: move out merge script to tools
parent
485f75b2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
27 additions
and
31 deletions
+27
-31
libav-merge.txt
doc/libav-merge.txt
+5
-31
libav-merge-next-commit
tools/libav-merge-next-commit
+22
-0
No files found.
doc/libav-merge.txt
View file @
95a7cbb0
...
...
@@ -71,37 +71,11 @@ a different merge conflict style:
$ git config --global merge.conflictstyle diff3
Here is a script to help merging the next commit in the queue:
#!/bin/sh
if [ "$1" != "merge" -a "$1" != "noop" ]; then
printf "Usage: $0 <merge|noop [REF_HASH]>\n"
exit 0
fi
[ "$1" = "noop" ] && merge_opts="-s ours"
nextrev=$(git rev-list libav/master --not master --no-merges | tail -n1)
if [ -z "$nextrev" ]; then
printf "Nothing to merge..\n"
exit 0
fi
printf "Merging $(git log -n 1 --oneline $nextrev)\n"
git merge --no-commit $merge_opts --no-ff --log $nextrev
if [ "$1" = "noop" -a -n "$2" ]; then
printf "\nThis commit is a noop, see $2\n" >> .git/MERGE_MSG
fi
printf "\nMerged-by: $(git config --get user.name) <$(git config --get user.email)>\n" >> .git/MERGE_MSG
The script assumes a remote named libav.
It has two modes: merge, and noop. The noop mode creates a merge with no change
to the HEAD. You can pass a hash as extra argument to reference a justification
(it is common that we already have the change done in FFmpeg).
tools/libav-merge-next-commit is a script to help merging the next commit in
the queue. It assumes a remote named libav. It has two modes: merge, and noop.
The noop mode creates a merge with no change to the HEAD. You can pass a hash
as extra argument to reference a justification (it is common that we already
have the change done in FFmpeg).
Also see tools/murge, you can copy and paste a 3 way conflict into its stdin
and it will display colored diffs. Any arguments to murge (like ones to suppress
...
...
tools/libav-merge-next-commit
0 → 100755
View file @
95a7cbb0
#!/bin/sh
if
[
"
$1
"
!=
"merge"
-a
"
$1
"
!=
"noop"
]
;
then
printf
"Usage:
$0
<merge|noop [REF_HASH]>
\n
"
exit
0
fi
[
"
$1
"
=
"noop"
]
&&
merge_opts
=
"-s ours"
nextrev
=
$(
git rev-list libav/master
--not
master
--no-merges
|
tail
-n1
)
if
[
-z
"
$nextrev
"
]
;
then
printf
"Nothing to merge..
\n
"
exit
0
fi
printf
"Merging
$(
git log
-n
1
--oneline
$nextrev
)
\n
"
git merge
--no-commit
$merge_opts
--no-ff
--log
$nextrev
if
[
"
$1
"
=
"noop"
-a
-n
"
$2
"
]
;
then
printf
"
\n
This commit is a noop, see
$2
\n
"
>>
.git/MERGE_MSG
fi
printf
"
\n
Merged-by:
$(
git config
--get
user.name
)
<
$(
git config
--get
user.email
)
>
\n
"
>>
.git/MERGE_MSG
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment