For example the following invocations are equivalent: git -git-dir=a.git -work-tree=b -C c status This option affects options that expect path name like -git-dir and -work-tree in that their interpretations of the path names would be made relative to the working directory caused by the -C option. C "", then the current working directory is left unchanged. When multiple -C options are given, each subsequent non-absolute -C is interpreted relative to the preceding -C.
Run as if git was started in instead of the current working directory. See the section called “git-help(1)” for more information, because git -help.
#Git annex tortoise manual#
Other options are available to control how the manual page is displayed. If a Git command is named this option will bring up the manual page for that command. If the option -all or -a is given then all available commands are printed.
Prints the synopsis and a list of the most commonly used commands. Branching? Fork defined as an "accidental" split of the check-in tree Branch defined as deliberate e.g.-version Prints the Git suite version that the git program came from.
#Git annex tortoise update#
f385, usually 8 letters) Folie 3Ĥ Fossil principles Fossil is leightweight Compilation is a matter of seconds, including SQLite code One executable 787kB including self-tests & documentation No dependency whatsoever on external libs or tools: gzip, diff, rsync, Python, Perl, Tcl, Java, Apache, Dbs, patch, Fossil is self-hosted The website runs on fossil as CGI Folie 5ĥ Usability: Command line interface Comfortable command-line interface Prefixes suffice for commands & AIDs fossil commit fossil rebuild fossil reconstruct fossil co = checkout fossil com fossil reb fossil rec fossil che Symbolic names for check-ins instead of an AID Simple tags on a check-in, starting with symfossil update my_feature_branch Folie 6Ħ Usability: Web interface Fossil runs as a web server, provides a comfortable interface fossil ui or fossil server Folie 7ħ Usability: Desktop interface not yet available Folie 8Ĩ Features Distributed version control system Similar to Mercurial & Bazaar (Python), Git (C), BitKeeper Very fast (pure C code) Data-efficient (stores and syncs (binary) deltas, zlib'ed) Fossil is safe: SQLite manages all data + BLOBs, transactional Extensive self-testing upon each action (zlib-(de)compress), checksumming for every artifact and every action Folie 9ĩ Features Very simple and persistent data structures for deltas, tables and file formats No need to dump data off a repository, because each repository is always exactly one file Migration very easy: close,, open No need to import dumped data, because upgrading a repository to a younger fossil executable is that easy: fossil all rebuild Folie 10ġ0 Fossil: Main building blocks (SCM) Fossil is a VCS, but additionally each repository contains A ticket system (bugtracker) History independent of check-in history A simple Wiki Each wiki page has its own history, independent of check-ins Pages can theoretically be branched and merged But currently no UI or ABI for that Embedded documentation linked with check-ins Reachable by /doc//.wiki CSS can be changed via admin options from the UI Folie 11ġ1 Tags can be attached to any leaf Can have a value (= property), but mostly need none Can be symbolic (starting with sym-) Are passed on to descendants Unless cancelled (fossil tag cancel ) Unless merging with another branch There are two default tags: branch=trunk represents the current branch sym-trunk (= NULL) symbolic name of branch After branching sym-trunk: cancelled Folie 12ġ2 Branching Forking vs.
#Git annex tortoise license#
Hipp - Author of License GPL v2 Motto No information shall ever get lost Folie 2ģ Fossil principles In Fossil, a revision is called check-in Every file, branch and check-in is an immutable artifact with an artifact identifier (AID), which is a SHA-1 hash E.g. 1 Integrated version control with Fossil SCM Tech Talk Arne Bachmann Folie 1Ģ Overview Web address Author Dr.
0 kommentar(er)
