Subversion Repositories Kolibri OS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Luckily Git comes with excellent documentation.

  man git

  man git-

All you need is to provide a ssh public key to the Git server admin.

guidelines. Read it at least once, if you are granted commit privileges to the

FFmpeg project you are expected to be familiar with these rules.

==========

  You can get git from http://git-scm.com/

  you push back your changes to the remote repository.

  can be remote. By default the master branch tracks the branch master in

  the remote origin.

  Caveat: Since merge commits are forbidden at least for the initial

          months of git --ff-only or --rebase (see below) are recommended.

          --ff-only will fail and not create merge commits if your branch

          has diverged (has a different history) from the tracked branch.

  over it. This is required to keep all your local changes at the top of

  FFmpeg's master tree. The master tree will reject pushes with merge commits.

    git rm [-r] 

  directory that makes files appear or disappear.

  Line moves across files are automatically tracked.

  interface available at http://source.ffmpeg.org

  of a commit (additions, modifications, deletions, etc.).

  on. All experienced developers do this on each and every commit, no matter

  how small.

  Every one of them has been saved from looking like a fool by this many times.

  It's very easy for stray debug output or cosmetic modifications to slip in,

  please avoid problems through this extra level of scrutiny.

    git config --global user.name "My Name"

    git config --global user.email my@email.invalid

  (--global to set the global configuration for all your git checkouts).

  the interactive or the patch mode to select hunk by hunk what should be

  added to the commit.

  set in your personal configuration file through

  GIT_EDITOR, VISUAL or EDITOR.

  what you did will be obvious from the changes themselves most of the time.

  Saying just "bug fix" or "10l" is bad. Remember that people of varying skill

  levels look at and educate themselves while reading through your code. Don't

  include filenames in log messages, Git provides that information.

  empty line and then a full description. The first line will be used to name

  the patch by git format-patch.

  discussing it on the mailing list first!

  commit disappear from the history.

  branch history.

  merge or remove some of them in the process.

  should use them ONLY on your local or topic branches.

  current HEAD. E.g.

  present in upstream.

  A useful shortcut is also

  By default the patches are created in the current directory.

  them. All the email fields can be configured in the global/local

  configuration or overridden by command line.

  Note that this tool must often be installed separately (e.g. git-email

  package on Debian-based distros).

  Git will prevent you from pushing changes if the local and remote trees are

  out of sync. Refer to 2 and 2.a to sync the local tree.

  to push your local branch for review on a remote host.

  push update all the remote branches matching the local ones.

  based on a regular expression. see man gitrevisions

  the git log output is the easiest option (especially if a pager with

  search capabilities is used).

  This commit can be checked out with

problems with the GIT server.