Free Knowledge Resources


Linux Manual Pages


Free Software * Books

Source Code

Free Media

Linux

git-send-pack(1)


NAME

   git-send-pack - Push objects over Git protocol to another repository

SYNOPSIS

   git send-pack [--all] [--dry-run] [--force] [--receive-pack=<git-receive-pack>]
                   [--verbose] [--thin] [--atomic]
                   [--[no-]signed|--sign=(true|false|if-asked)]
                   [<host>:]<directory> [<ref>...]

DESCRIPTION

   Usually you would want to use git push, which is a higher-level wrapper
   of this command, instead. See git-push(1).

   Invokes git-receive-pack on a possibly remote repository, and updates
   it from the current repository, sending named refs.

OPTIONS

   --receive-pack=<git-receive-pack>
       Path to the git-receive-pack program on the remote end. Sometimes
       useful when pushing to a remote repository over ssh, and you do not
       have the program in a directory on the default $PATH.

   --exec=<git-receive-pack>
       Same as --receive-pack=<git-receive-pack>.

   --all
       Instead of explicitly specifying which refs to update, update all
       heads that locally exist.

   --stdin
       Take the list of refs from stdin, one per line. If there are refs
       specified on the command line in addition to this option, then the
       refs from stdin are processed after those on the command line.

       If --stateless-rpc is specified together with this option then the
       list of refs must be in packet format (pkt-line). Each ref must be
       in a separate packet, and the list must end with a flush packet.

   --dry-run
       Do everything except actually send the updates.

   --force
       Usually, the command refuses to update a remote ref that is not an
       ancestor of the local ref used to overwrite it. This flag disables
       the check. What this means is that the remote repository can lose
       commits; use it with care.

   --verbose
       Run verbosely.

   --thin
       Send a "thin" pack, which records objects in deltified form based
       on objects not included in the pack to reduce network traffic.

   --atomic
       Use an atomic transaction for updating the refs. If any of the refs
       fails to update then the entire push will fail without changing any
       refs.

   --[no-]signed, --sign=(true|false|if-asked)
       GPG-sign the push request to update refs on the receiving side, to
       allow it to be checked by the hooks and/or be logged. If false or
       --no-signed, no signing will be attempted. If true or --signed, the
       push will fail if the server does not support signed pushes. If set
       to if-asked, sign if and only if the server supports signed pushes.
       The push will also fail if the actual call to gpg --sign fails. See
       git-receive-pack(1) for the details on the receiving end.

   <host>
       A remote host to house the repository. When this part is specified,
       git-receive-pack is invoked via ssh.

   <directory>
       The repository to update.

   <ref>...
       The remote refs to update.

SPECIFYING THE REFS

   There are three ways to specify which refs to update on the remote end.

   With --all flag, all refs that exist locally are transferred to the
   remote side. You cannot specify any <ref> if you use this flag.

   Without --all and without any <ref>, the heads that exist both on the
   local side and on the remote side are updated.

   When one or more <ref> are specified explicitly (whether on the command
   line or via --stdin), it can be either a single pattern, or a pair of
   such pattern separated by a colon ":" (this means that a ref name
   cannot have a colon in it). A single pattern <name> is just a shorthand
   for <name>:<name>.

   Each pattern pair consists of the source side (before the colon) and
   the destination side (after the colon). The ref to be pushed is
   determined by finding a match that matches the source side, and where
   it is pushed is determined by using the destination side. The rules
   used to match a ref are the same rules used by git rev-parse to resolve
   a symbolic ref name. See git-rev-parse(1).

   *   It is an error if <src> does not match exactly one of the local
       refs.

   *   It is an error if <dst> matches more than one remote refs.

   *   If <dst> does not match any remote ref, either

       *   it has to start with "refs/"; <dst> is used as the destination
           literally in this case.

       *   <src> == <dst> and the ref that matched the <src> must not
           exist in the set of remote refs; the ref matched <src> locally
           is used as the name of the destination.

   Without '--force`, the <src> ref is stored at the remote only if <dst>
   does not exist, or <dst> is a proper subset (i.e. an ancestor) of
   <src>. This check, known as "fast-forward check", is performed in order
   to avoid accidentally overwriting the remote ref and lose other
   peoples' commits from there.

   With --force, the fast-forward check is disabled for all refs.

   Optionally, a <ref> parameter can be prefixed with a plus + sign to
   disable the fast-forward check only on that ref.

GIT

   Part of the git(1) suite



Opportunity


Personal Opportunity - Free software gives you access to billions of dollars of software at no cost. Use this software for your business, personal use or to develop a profitable skill. Access to source code provides access to a level of capabilities/information that companies protect though copyrights. Open source is a core component of the Internet and it is available to you. Leverage the billions of dollars in resources and capabilities to build a career, establish a business or change the world. The potential is endless for those who understand the opportunity.

Business Opportunity - Goldman Sachs, IBM and countless large corporations are leveraging open source to reduce costs, develop products and increase their bottom lines. Learn what these companies know about open source and how open source can give you the advantage.



Free Software


Free Software provides computer programs and capabilities at no cost but more importantly, it provides the freedom to run, edit, contribute to, and share the software. The importance of free software is a matter of access, not price. Software at no cost is a benefit but ownership rights to the software and source code is far more significant.

Free Office Software - The Libre Office suite provides top desktop productivity tools for free. This includes, a word processor, spreadsheet, presentation engine, drawing and flowcharting, database and math applications. Libre Office is available for Linux or Windows.



Free Books


The Free Books Library is a collection of thousands of the most popular public domain books in an online readable format. The collection includes great classical literature and more recent works where the U.S. copyright has expired. These books are yours to read and use without restrictions.

Source Code - Want to change a program or know how it works? Open Source provides the source code for its programs so that anyone can use, modify or learn how to write those programs themselves. Visit the GNU source code repositories to download the source.



Education


Study at Harvard, Stanford or MIT - Open edX provides free online courses from Harvard, MIT, Columbia, UC Berkeley and other top Universities. Hundreds of courses for almost all major subjects and course levels. Open edx also offers some paid courses and selected certifications.

Linux Manual Pages - A man or manual page is a form of software documentation found on Linux/Unix operating systems. Topics covered include computer programs (including library and system calls), formal standards and conventions, and even abstract concepts.


birds banner