![]() ![]() If you want to create a cover letter for multiple patches use: If you have been developing on vlc locally and (still) don't have write access, you can submit all your commits in one shot using: Use a graphical interface $ gitk # Tree Browserįirst make sure you have read our Sending Patches page. ![]() Keeping your local working branch in sync $ git pull -rebase If you wish to give credit to someone else's work (e.g. As soon as you feel you have reached a step in development where you can commit your work locally, use List your local non committed changes $ git status | less You can now list your local branch by doing "git checkout -f master" if you think your tree is pretty hopeless, need a kill-and-fill to bring the master into your local repository.Use "git stash apply" to get your stash back. Do this if you think there may be other commits against the same things you are working on and want to refresh your local checkout (using a git pull -rebase) from the master. "git stash" if you want to "hide" your changes."git push" to move your changes up to the master."git log origin.master" to check what you are going to commit."git pull -rebase" or "git up" (if you did git config -global alias.up "pull -rebase") to bring the rest of your local repository up to date."git commit" the changes in your local repository.Make your file edits in your local repository.Just set up a post-checkout hook accordingly. If you are using Qt-creator and want to keep your files listing in sync, $ git config -global alias.wup "log -p use: If you want to see what you are about to "git push", along with the diff: Setting up "git wup" (Git What's Up - with patch) (Tip) Note that this only works for the master branch. $ git config -global alias.wu "log -stat use: If you want to see what you are about to "git push": Setting up "git wu" (Git What's Up) (Tip) $ git config -global alias.up '!sh -c "git commit -a -m "Before rebase" & git pull -rebase & git reset head^"' $ git config -global alias.up "pull -rebase"Īnd if you like your tree to be messy and don't want git to complain (like in svn) use: If you want to be able to just keep in sync using "git up" use: If you are using an old git version (prior to 1.5.5) and previous command didn't work, use: If you want to use git with colored output use: If errors occur telling you something like perl's SMTP::SSL package is not there. $ git config -global sendemail.smtpserverport 587 $ git config -global sendemail.smtpencryption tls $ git config -global sendemail.smtpuser your-gmail-address-here $ git config -global sendemail.smtpserver If you receive a cannot set X509 trust file error when using another CA certificate, make sure it is in the PEM (text format) rather than DER format (binary). The certificate for gmail can be found here: EquifaxSecureCertificateAuthority.crt $ git config -global sendemail.smtpserver /usr/local/bin/msmtp The password will be asked for upon sending mail. Tls_trust_file /certificates/EquifaxSecureCertificateAuthority.crt # Set default values for all following accounts. Install it with tls and ssl activated and place the following config file (.msmtprc) in your home directory Git-send-email -annotate -smtp-server= -smtp-server-port=587 -smtp-encryption=tls You'll need a command line similar to the following one: Git-send-email has built in support for sending e-mail through SMTP. To send patches you'll need a working git-send-email configuration. $ git config -global user.name "Your Name" You can also browse the sources on GitLab.ġ.4.4.2 Requires the repo-config command rather than just config Personal Information You can also clone using http via our repo.or.cz mirror. Or via http protocol from github (github can sometimes be a bit behind as a mirror): Voilà! You got the stable branch repository. $ git clone -single-branch -branch 3.0.x You can find the stable VLC version in the 3.0.x branch, to check just that out use: ![]() If you want only the last 3 VLC revisions:Ĭlones without the full revision set (-depth) can't be used for backporting (or to make sure that you're including at least commits up to the common fork point). Voilà! The full x264 history should be on your hard disk in x264/. Voilà! The full VLC history should be on your hard disk in vlc/. Getting VLC or x264 source code via Git $ git clone ![]() If you are using Windows, please read the Git Windows page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |