Lines Matching +full:windows +full:- +full:remote +full:- +full:only

1 \input texinfo @c -*- texinfo -*-
2 @documentencoding UTF-8
21 git --help
28 git <command> --help
29 man git-<command>
38 @url{http://git-scm.com/, Git website}.
42 What follows now is a basic introduction to Git and some FFmpeg-specific
49 You can get Git from @url{http://git-scm.com/}
66 you push back your changes to the remote repository.
69 git clone gil@@ffmpeg.org:ffmpeg-web <target>
73 @var{<target>} and let you push back your changes to the remote repository.
76 If you don't have write-access to the ffmpeg-web repository, you can
77 create patches after making a read-only ffmpeg-web clone:
80 git clone git://ffmpeg.org/ffmpeg-web <target>
83 Make sure that you do not have Windows line endings in your checkouts,
88 git config --global core.autocrlf false
96 git pull (--rebase)
100 can be remote. By default the master branch tracks the branch master in
101 the remote origin.
104 @command{--rebase} (see below) is recommended.
110 git pull --rebase
121 git add [-A] <filename/dirname>
122 git rm [-r] <filename/dirname>
161 git diff --check
172 For cosmetics-only commits you should get (almost) empty output from
175 git diff -w -b <filename(s)>
187 git add [-i|-p|-A] <filenames/dirnames>
193 git config --global user.name "My Name"
194 git config --global user.email my@@email.invalid
195 git config --global user.signingkey ABCDEF0123245
198 Enable signing all commits or use -S
201 git config --global commit.gpgsign true
204 Use @option{--global} to set the global configuration for all your Git checkouts.
221 git config --global core.editor
233 separated by an empty line. These details should not exceed 60-72 characters
261 the patch by @command{git format-patch}.
263 Common mistakes for the first line, as seen in @command{git log --oneline}
270 git format-patch <commit> [-o directory]
277 git format-patch origin/master
285 git format-patch -n
294 git send-email <commit list|directory>
297 will send the patches created by @command{git format-patch} or directly
300 Note that this tool must often be installed separately (e.g. @var{git-email}
301 package on Debian-based distros).
310 git add [-A] .
322 Add the following to your @file{~/.gitconfig} to help @command{git send-email}
323 and @command{git format-patch} detect renames:
332 In order to have @command{git send-email} automatically send patches
333 to the ffmpeg-devel mailing list, add the following stanza
338         to = ffmpeg-devel@@ffmpeg.org
353 git commit --amend
359 git rebase -i origin/master
366 @command{git reset}, @command{git commit --amend} and @command{git rebase}
367 rewrite history, so you should use them ONLY on your local or topic branches.
378 @section Pushing changes to remote trees
381 git push origin master --dry-run
384 Will simulate a push of the local master branch to the default remote
387 Git will prevent you from pushing changes if the local and remote trees are
391 git remote add <name> <url>
394 Will add additional remote with a name reference, it is useful if you want
395 to push your local branch for review on a remote host.
398 git push <remote> <refspec>
401 Will push the changes to the @var{<remote>} repository.
402 Omitting @var{<refspec>} makes @command{git push} update all the remote
421 git checkout -b svn_23456 :/'as revision 23456'
427 git checkout -b svn_23456 $SHA1
439 gpg --default-new-key-algo "ed25519/cert,sign+cv25519/encr" --quick-generate-key "human@@server.com"
446 @chapter Pre-push checklist
457 with @option{--dry-run} first. And then inspecting the commits listed with
458 @command{git log -p 1234567..987654}. The @command{git status} command
467 @item if fate fails due to missing samples run @command{make fate-rsync} and retry
471 test suite only checks against regressions and that only to some extend. It does
479 merge request to ffmpeg-devel. You can also push them directly but this is not