giteveryday – A useful minimum set of commands for Everyday Git Synopsis Everyday Git With 20 Commands Or So Description Git users can broadly be grouped into four categories for the purposes of describing here a small set of useful command for everyday Git. • Individual Developer (Standalone) commands are essential for anybody who makes…
gitdiffcore – Tweaking diff output Synopsis git diff * Description The diff commands git diff-index, git diff-files, and git diff-tree can be told to manipulate differences they find in unconventional ways before showing diff output. The manipulation is collectively called "diffcore transformation". This short note describes what they are and how to use them to…
gitcvs-migration – Git for CVS users Synopsis git cvsimport * Description Git differs from CVS in that every working tree contains a repository with a full copy of the project history, and no repository is inherently more important than any other. However, you can emulate the CVS model by designating a single shared repository which…
gitcredentials – Providing usernames and passwords to Git Synopsis git config credential.https://example.com.username myusername git config credential.helper "$helper $options" Description Git will sometimes need credentials from the user in order to perform operations; for example, it may need to ask for a username and password in order to access a remote repository over HTTP. This manual…
gitcore-tutorial – A Git core tutorial for developers Synopsis git * Description This tutorial explains how to use the "core" Git commands to set up and work with a Git repository. If you just need to use Git as a revision control system you may prefer to start with "A Tutorial Introduction to Git" (gittutorial(7))…
gitcli – Git command-line interface and conventions Synopsis gitcli Description This manual describes the convention used throughout Git CLI. Many commands take revisions (most often "commits", but sometimes "tree-ish", depending on the context and command) and paths as their arguments. Here are the rules: • Revisions come first and then paths. E.g. in git diff…
ggz – The GGZ Gaming Zone Description The GGZ Gaming Zone is a standards-conforming free online gaming infrastructure which provides many applications and games to people who like to play on the internet or in local networks. GGZ, how the (recursive) acronym is called, is available for many computer systems. This document focuses on the…
gammu-smsd-tables – description of tables for database backends of gammu-smsd(1) Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). Separate backends are described in their appropriate man pages. This manual page describes general database structure and required tables. More SMS daemons can share single database. If you do not specify…
gammu-smsd-pgsql – gammu-smsd(1) backend using PostgreSQL database server as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). PGSQL backend stores all data in a PostgreSQL database server, which parameters are defined by configuration (see gammu-smsdrc(5) for description of configuration options). For tables description see gammu-smsd-tables(7). See…
gammu-smsd-mysql – gammu-smsd(1) backend using MySQL database server as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). MYSQL backend stores all data in a MySQL database server, which parameters are defined by configuration (see gammu-smsdrc(5) for description of configuration options). For tables description see gammu-smsd-tables(7). See…
gammu-smsd-files – gammu-smsd(1) backend using filesystem as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). FILES backend stores all data on a filesystem in folders defined by configuration (see gammu-smsdrc(5) for description of configuration options). Limitation FILES backend does not support gammu-smsd-inject(1) program. This support might…
gammu-smsd-dbi – gammu-smsd(1) backend using DBI abstraction layer to use any supported database as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). DBI backend stores all data in any database supported by libdbi, which parameters are defined by configuration (see gammu-smsdrc(5) for description of configuration options)….
futex – fast user-space locking Synopsis #include <linux/futex.h> Description The Linux kernel provides futexes ("Fast user-space mutexes") as a building block for fast user-space locking and semaphores. Futexes are very basic and lend themselves well for building higher-level locking abstractions such as mutexes, condition variables, read-write locks, barriers, and semaphores. Most programmers will in fact…
feature_test_macros – feature test macros Description Feature test macros allow the programmer to control the definitions that are exposed by system header files when a program is compiled. NOTE: In order to be effective, a feature test macro must be defined before including any header files. This can be done either in the compilation command…
frysk – The Frysk Debugging, Tracing, and Monitoring Tool Suite Description The Frysk Tool Suite provides a collection of command line and gnome utilities for the debugging, tracing, and monitoring of user programs. See Also funit(8) fauxv(1) fcatch(1) fcore(1) fdebuginfo(1) ferror(1) fexe(1) fhpd(1) fmaps(1) fparser(1) fstack(1) fstep(1) ftrace(1) fdebugrpm(1) Bugs Report bugs to m[blue]http://sourceware.org/fryskm[]
frontend-spec – interface between jw and its frontends Description jw(1) calls frontends like frontends/docbook to get the informations specific to a given input format. The frontend knows which information to return from the first command line parameter. It gets all necessary data via environment variables ready to use. This document describes that command line parameter…
FreeIPMI – FreeIPMI overview Introduction FreeIPMI provides in-band and out-of-band IPMI software based on the IPMI v1.5/2.0 specification. What is IPMI? The IPMI specification defines a set of interfaces for platform management and is implemented by a number vendors for system management. The features of IPMI that most users will be interested in are sensor…
filter – cups file conversion filter interface Synopsis filter job user title num – copies options [filename ] #include <cups/cups.h> ssize_t cupsBackChannelRead(char *buffer, size_t bytes, double timeout); cups_sc_status_t cupsSideChannelDoRequest(cups_sc_command_t command, char *data, int *datalen, double timeout); #include <cups/ppd.h> const char *cupsGetOption(const char *name, int num_options, cups_option_t *options); int cupsMarkOptions(ppd_file_t *ppd, int num_options, cups_option_t *options); int…
filesystem – event signalling that filesystems have been mounted Synopsis filesystem [ENV]… Description The filesystem event is generated by the mountall(8) daemon after it has mounted all filesystems listed in fstab(5). mountall(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other…
file-hierarchy – File system hierarchy overview Description Operating systems using the systemd(1) system and service manager are organized based on a file system hierarchy inspired by UNIX, more specifically the hierarchy described in the m[blue]File System Hierarchym[][1] specification and hier(7), with various extensions, partially documented in the m[blue]XDG Base Directory Specificationm[][2] and m[blue]XDG User Directoriesm[][3]….