bt-obex(1) [debian man page]

bt-obex(1)							    bluez-tools 							bt-obex(1)

NAME

       bt-obex - a bluetooth OBEX client/server

SYNOPSIS

       bt-obex [OPTION...]

       Help Options:
	 -h, --help

       Application Options:
	 -a, --adapter=<name|mac>
	 -s, --server [<path>]
	 -p, --opp <name|mac> <file>
	 -f, --ftp=<name|mac>

DESCRIPTION

       This utility implemented support of Object Push Profile (OPP) and File Transfer Profile (FTP).  You can send and receive files to/from
       remote device using this tool.

OPTIONS

       -h, --help
	   Show help

       -a, --adapter <name|mac>
	   Specify adapter to use by his Name or MAC address
	   (if this option does not defined - default adapter used)

       -s, --server [<path>]
	   Register agent at OBEX server and set incoming/root directory to
	   `path` or current folder will be used; Agent is used to
	   accept/reject incoming bluetooth object push requests

       -p, --opp <name|mac> <file>
	   Send local file to the specified remote device using object push
	   profile

       -f, --ftp <name|mac>
	   Start FTP session with remote device; If session opened
	   successfuly, FTP shell will be opened

	   FTP commands:

	       help		       Show help message
	       exit		       Close FTP session
	       cd <folder>	       Change the current folder of the remote device
	       mkdir <folder>	       Create a new folder in the remote device
	       ls		       List folder contents
	       get <src> <dst>	       Copy the src file (from remote device) to the dst file (on local filesystem)
	       put <src> <dst>	       Copy the src file (from local filesystem) to the dst file (on remote device)
	       cp <src> <dst>	       Copy a file within the remote device from src file to dst file
	       mv <src> <dst>	       Move a file within the remote device from src file to dst file
	       rm <target>	       Deletes the specified file/folder

AUTHOR

       Alexander Orlenko <zxteam@gmail.com>.

SEE ALSO

       bt-adapter(1) bt-agent(1) bt-audio(1) bt-device(1) bt-input(1) bt-monitor(1) bt-network(1) bt-serial(1)

								    2010-08-16								bt-obex(1)

GIT-HTTP-PUSH(1)						    Git Manual							  GIT-HTTP-PUSH(1)

NAME

       git-http-push - Push objects over HTTP/DAV to another repository

SYNOPSIS

       git http-push [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...]

DESCRIPTION

       Sends missing objects to remote repository, and updates the remote branch.

       NOTE: This command is temporarily disabled if your libcurl is older than 7.16, as the combination has been reported not to work and
       sometimes corrupts repository.

OPTIONS

       --all
	   Do not assume that the remote repository is complete in its current state, and verify all objects in the entire local ref's history
	   exist in the remote repository.

       --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.

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

       --verbose
	   Report the list of objects being walked locally and the list of objects successfully sent to the remote repository.

       -d, -D
	   Remove <ref> from remote repository. The specified branch cannot be the remote HEAD. If -d is specified the following other conditions
	   must also be met:

	   o   Remote HEAD must resolve to an object that exists locally

	   o   Specified branch resolves to an object that exists locally

	   o   Specified branch is an ancestor of the remote HEAD

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

SPECIFYING THE REFS

       A <ref> specification can be either a single pattern, or a pair of such patterns 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.

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

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

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

	   o   <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

Git 2.17.1							    10/05/2018							  GIT-HTTP-PUSH(1)