amqp-publish(1) [debian man page]

AMQP-PUBLISH(1) 						 RabbitMQ C Client						   AMQP-PUBLISH(1)

NAME

       amqp-publish - Publish a message on an AMQP server

SYNOPSIS

       amqp-publish [OPTION...]

DESCRIPTION

       Publishes a message to an exchange on an AMQP server. Options allow the various properties of the message and parameters of the AMQP
       basic.publish method to be specified.

       By default, the message body is read from standard input. Alternatively, the -b option allows the message body to be provided as part of
       the command.

OPTIONS

       -e, --exchange=exchange name
	   The name of the exchange to publish to. If omitted, the default exchange (also known as the nameless exchange) is used.

       -r, --routing-key=routing key
	   The routing key to publish with. If omitted, an empty routing key is assumed. A routing key must be specified when publishing to the
	   default exchange; in that case, accoding to the AMQP specification, the routing key corresponds to a queue name.

       -p, --persistent
	   Use the persistent delivery mode. Without this option, non-persistent delivery is used.

       -C, --content-type=MIME type
	   Specifies the content-type property for the message. If omitted, the content-type property is not set on the message.

       -E, --content-encoding=content coding
	   Specifies the content-encoding property for the message. If omitted, the content-encoding property is not set on the message.

       -b, --body=message body
	   Specifies the message body. If omitted, the message body is read from standard input.

EXAMPLES

       Send a short message, consisting of the word "Hello" to the queue "myqueue" via the default exchange:

	       $ amqp-publish -r myqueue -b Hello

       Send some XML data from a file to the exchange "events", with persistent delivery mode, setting the content-type property on the message to
       make the data format explicit:

	       $ amqp-publish -e events -p -C text/xml <event.xml

SEE ALSO

       librabbitmq-tools(7) describes connection-related options common to all the RabbitMQ C Client tools.

AUTHOR

       The RabbitMQ Team <info@rabbitmq.com>

RabbitMQ C Client						    2011-01-01							   AMQP-PUBLISH(1)

STG-PUBLISH(1)							   StGit Manual 						    STG-PUBLISH(1)

NAME

       stg-publish - Push the stack changes to a merge-friendly branch

SYNOPSIS

       stg publish [options] [branch]

DESCRIPTION

       This command commits a set of changes on a separate (called public) branch based on the modifications of the given or current stack. The
       history of the public branch is not re-written, making it merge-friendly and feasible for publishing. The heads of the stack and public
       branch may be different but the corresponding tree objects are always the same.

       If the trees of the stack and public branch are different (otherwise the command has no effect), StGit first checks for a rebase of the
       stack since the last publishing. If a rebase is detected, StGit creates a commit on the public branch corresponding to a merge between the
       new stack base and the latest public head.

       If no rebasing was detected, StGit checks for new patches that may have been created on top of the stack since the last publishing. If new
       patches are found and are not empty, they are checked into the public branch keeping the same commit information (e.g. log message, author,
       committer, date).

       If the above tests fail (e.g. patches modified or removed), StGit creates a new commit on the public branch having the same tree as the
       stack but the public head as its parent. The editor will be invoked if no "--message" option is given.

       It is recommended that stack modifications falling in different categories as described above are separated by a publish command in order
       to keep the public branch history cleaner (otherwise StGit would generate a big commit including several stack modifications).

       The public branch name can be set via the branch.<branch>.public configuration variable (defaulting to "<branch>.public").

OPTIONS

       -b BRANCH, --branch BRANCH
	   Use BRANCH instead of the default branch.

       --author "NAME <EMAIL>"
	   Set the author details.

       --authname NAME
	   Set the author name.

       --authemail EMAIL
	   Set the author email.

       --authdate DATE
	   Set the author date.

       -m MESSAGE, --message MESSAGE
	   Use MESSAGE instead of invoking the editor.

       -f FILE, --file FILE
	   Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)

       --sign
	   Add a "Signed-off-by:" to the end of the patch.

       --ack
	   Add an "Acked-by:" line to the end of the patch.

STGIT

       Part of the StGit suite - see linkman:stg[1]

StGit								    03/13/2012							    STG-PUBLISH(1)