pijul/manual - Change 2AYYR6FKMBQ7FS2U5DNFGZCYPJ2A2L7WSXKHIIYPHV5UWPM4VYYAC

Delete auto-generated files, now that this is taken care of in the deployment scripts

Created by pmeunier on November 23, 2020

2AYYR6FKMBQ7FS2U5DNFGZCYPJ2A2L7WSXKHIIYPHV5UWPM4VYYAC

Dependencies

In channels

main

Change contents

File deletion: add.md

BF:BFD[3.49554] → [3.82087:82095]

BF:BFD[3.82095] → [3.82096:82096]

B:BD[3.82096] → [3.82097:83102]

# pijul add
Add files and directories to the tree
## Usage
```cmd
pijul add [-h | --help] [--recursive] [-V | --version] [--repository <repository>] [<file>…]
```
## Description
Adds directories and files to the
[tree](./getting_started.html#definitions), which is the set of files
currently tracked by Pijul.
The tree's structure is supposed to mirror almost exactly the
filesystem, with a few extra bits of information to synchronise it
with the pristine.
## Example
When starting a Rust project, it is common to add `Cargo.toml` and
`src/lib.rs` from the repository root:
```
pijul add Cargo.toml src/lib.rs
```
## Options
- -h, --help
  Print a help message and exit.
- --recursive
  Recursively add all the files in the directories in argument \<file\>…
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- \<file\>…
  A list of files to add to the tree.

File deletion: add.md

BF:BFD[3.49554] → [4.21785:21793]

BF:BFD[4.21793] → [4.21794:21794]

B:BD[4.21794] → [4.21795:22033]

∅:BD[2.3247] → [4.22033:22034]

B:BD[4.22033] → [4.22033:22034]

B:BD[4.22034] → [2.3248:3332]

∅:BD[2.3332] → [4.22068:22093]

B:BD[4.22068] → [4.22068:22093]

∅:BD[2.3349] → [4.22093:22094]

B:BD[4.22093] → [4.22093:22094]

B:BD[4.22094] → [2.3350:3414]

∅:BD[2.3414] → [4.22118:22135]

B:BD[4.22118] → [4.22118:22135]

∅:BD[2.3434] → [4.22135:22136]

B:BD[4.22135] → [4.22135:22136]

B:BD[4.22136] → [2.3435:3505]

∅:BD[2.3505] → [4.22163:22206]

B:BD[4.22163] → [4.22163:22206]

B:BD[4.22206] → [2.3506:3539]

∅:BD[2.3539] → [4.22347:22348]

B:BD[4.22347] → [4.22347:22348]

B:BD[4.22348] → [2.3540:3851]

∅:BD[2.3851] → [4.22368:22369]

B:BD[4.22368] → [4.22368:22369]

B:BD[4.22369] → [2.3852:3853]

B:BD[4.22135] → [2.3415:3434]

B:BD[4.22093] → [2.3333:3349]

B:BD[4.22033] → [2.3231:3247]

# pijul add
Adds a path to the tree.
Pijul has an internal tree to represent the files currently tracked. This command adds files and
directories to that tree.
##  Usage
```
pijul add [OPTIONS] [paths]...
```
##  Args
`<paths>...`
`Paths to add to the internal tree`
            Paths to add to the internal tree
##  Flags
`-h, --help`
`Prints help information`
            Prints help information
`-V, --version`
`Prints version information`
            Prints version information
##  Options
`--repository <repo-path>`
        --repository <repo-path>
`Set the repository in which paths must be added. Defaults to the first ancestor of the`
            Set the repository in which paths must be added. Defaults to the first ancestor of the
`current directory that contains a `.pijul` directory`
            current directory that contains a `.pijul` directory
    -V, --version
    -h, --help
    <paths>...

File deletion: apply.md

BF:BFD[3.49554] → [3.80714:80724]

BF:BFD[3.80724] → [3.80725:80725]

B:BD[3.80725] → [3.80726:82086]

# pijul apply
Apply patches by their hash or patch file
## Usage
```cmd
pijul apply [-h | --help] [-V | --version] [--repository <repository>] [--branch <branch>] [<patch>…]
```
## Description
This command is essentially meant to be called by [pijul
push](./reference/push.html) over SSH.
It applies patches to a branch in the pristine, either to the current
branch (if `--branch` is not specified), or to branch \<branch\>.
If that branch does not exist, it will be created.
\<patch\> must be a list of patch hashes or internal identifiers. If
empty, gzipped-compressed patch files are read from the standard
input. In other words, running `pijul apply hashhashhash` is
equivalent on Unix to running `cat .pijul/patches/hashhashhash.gz |
pijul apply`.
## Example
Apply the first patch in Pijul's development repository:
```
pijul apply AbaeCc9Y9jxGRgkapqjMv66dfZEvSUf3biXZa2LpcYx-CY646dQ9HFmL4R6x9Mez_cCz5QwW4w38P1O4bwVsjjI
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --branch \<branch\>
  Apply the patches to branch \<branch\> instead of the current branch.
- \<patch\>…
  A list of patch hash or internal identifiers to apply to the branch.

File deletion: apply.md
BF:BFD[3.49554] → [4.21471:21481]
BF:BFD[4.21481] → [4.21482:21482]
B:BD[4.21482] → [4.21483:21609]
∅:BD[2.3138] → [4.21609:21637]
B:BD[4.21609] → [4.21609:21637]
B:BD[4.21674] → [4.21674:21675]
B:BD[4.21675] → [2.3139:3223]
∅:BD[2.3223] → [4.21718:21755]
B:BD[4.21718] → [4.21718:21755]
∅:BD[2.3226] → [4.21755:21783]
B:BD[4.21755] → [4.21755:21783]
∅:BD[2.3228] → [4.21783:21784]
B:BD[4.21783] → [4.21783:21784]
B:BD[4.21784] → [2.3229:3230]
B:BD[4.21783] → [2.3227:3228]
B:BD[4.21755] → [2.3224:3226]
B:BD[4.21609] → [2.3136:3138]
```
# pijul apply
Applies one channel to other
##  Usage
```
pijul apply [FLAGS] [OPTIONS] [change]
```
##  Args
`<change>`
##  Flags
`--deps-only`
`-h, --help`
Prints help information
`-V, --version`
Prints version information
##  Options
`--channel <channel>`
`--repository <repo-path>`
```
File deletion: archive.md
BF:BFD[3.49554] → [4.21059:21071]
BF:BFD[4.21071] → [4.21072:21072]
B:BD[4.21072] → [4.21073:21201]
∅:BD[2.2980] → [4.21201:21202]
B:BD[4.21201] → [4.21201:21202]
B:BD[4.21202] → [2.2981:3055]
∅:BD[2.3055] → [4.21239:21240]
B:BD[4.21239] → [4.21239:21240]
B:BD[4.21240] → [2.3056:3083]
∅:BD[2.3083] → [4.21312:21350]
B:BD[4.21312] → [4.21312:21350]
∅:BD[2.3086] → [4.21350:21373]
B:BD[4.21350] → [4.21350:21373]
∅:BD[2.3088] → [4.21373:21374]
B:BD[4.21373] → [4.21373:21374]
B:BD[4.21374] → [2.3089:3105]
∅:BD[2.3105] → [4.21384:21404]
B:BD[4.21384] → [4.21384:21404]
∅:BD[2.3108] → [4.21404:21425]
B:BD[4.21404] → [4.21404:21425]
∅:BD[2.3111] → [4.21425:21454]
B:BD[4.21425] → [4.21425:21454]
B:BD[4.21454] → [2.3112:3135]
B:BD[4.21425] → [2.3109:3111]
B:BD[4.21404] → [2.3106:3108]
B:BD[4.21373] → [2.3087:3088]
B:BD[4.21350] → [2.3084:3086]
B:BD[4.21201] → [2.2966:2980]
```
# pijul archive
Creates an archive of the repository
##  Usage
```
pijul archive [FLAGS] [OPTIONS] -o <name>
```
##  Flags
Prints help information
`-k`
Do not check certificates
`-V, --version`
Prints version information
##  Options
`--change <change>...`
`--channel <channel>`
`-o <name>`
`--prefix <prefix>`
`--remote <remote>`
`--repository <repo-path>`
`--state <state>`
`-h, --help`
```
File deletion: change.md
BF:BFD[3.49554] → [4.20754:20765]
BF:BFD[4.20765] → [4.20766:20766]
B:BD[4.20766] → [4.20767:20898]
∅:BD[2.2874] → [4.20898:20910]
B:BD[4.20898] → [4.20898:20910]
∅:BD[2.2889] → [4.20910:20911]
B:BD[4.20910] → [4.20910:20911]
B:BD[4.20911] → [2.2890:2914]
∅:BD[2.2914] → [4.20948:20949]
B:BD[4.20948] → [4.20948:20949]
B:BD[4.20949] → [2.2915:2959]
∅:BD[2.2959] → [4.20992:21030]
B:BD[4.20992] → [4.20992:21030]
∅:BD[2.2962] → [4.21030:21058]
B:BD[4.21030] → [4.21030:21058]
B:BD[4.21058] → [2.2963:2965]
B:BD[4.21030] → [2.2960:2962]
B:BD[4.20910] → [2.2875:2889]
B:BD[4.20898] → [2.2872:2874]
```
# pijul change
Shows information about a particular change
##  Usage
```
pijul change [OPTIONS] [hash]
```
##  Args
`<hash>`
##  Flags
Prints help information
`-V, --version`
Prints version information
##  Options
`--channel <channel>`
`--repository <repo-path>`
`-h, --help`
```
File deletion: channel.md
BF:BFD[3.49554] → [4.20229:20241]
BF:BFD[4.20241] → [4.20242:20242]
B:BD[4.20242] → [4.20243:20356]
∅:BD[2.2564] → [4.20356:20357]
B:BD[4.20356] → [4.20356:20357]
B:BD[4.20357] → [2.2565:2581]
∅:BD[2.2581] → [4.20394:20395]
B:BD[4.20394] → [4.20394:20395]
B:BD[4.20395] → [2.2582:2609]
∅:BD[2.2609] → [4.20438:20480]
B:BD[4.20438] → [4.20438:20480]
∅:BD[2.2612] → [4.20480:20499]
B:BD[4.20480] → [4.20480:20499]
B:BD[4.20499] → [2.2613:2622]
∅:BD[2.2622] → [4.20570:20571]
B:BD[4.20570] → [4.20570:20571]
B:BD[4.20571] → [2.2623:2693]
∅:BD[2.2693] → [4.20637:20638]
B:BD[4.20637] → [4.20637:20638]
B:BD[4.20638] → [2.2694:2781]
∅:BD[2.2781] → [4.20664:20665]
B:BD[4.20664] → [4.20664:20665]
B:BD[4.20665] → [2.2782:2791]
∅:BD[2.2791] → [4.20752:20753]
B:BD[4.20752] → [4.20752:20753]
B:BD[4.20753] → [2.2792:2871]
B:BD[4.20480] → [2.2610:2612]
B:BD[4.20356] → [2.2525:2564]
```
# pijul channel
Manages different channels
##  Usage
```
pijul channel [OPTIONS] [SUBCOMMAND]
```
##  Flags
`-V, --version`
Prints version information
##  Options
`--repository <repo-path>`
##  Subcommands
`delete`
Delete a channel. The channel must not be the current channel
`help`
Prints this message or the help of the given subcommand(s)
`rename`
Rename a channel
`switch`
Switch to a channel. There must not be unrecorded changes in the working copy
`-h, --help`
Prints help information
```

File deletion: clone.md

BF:BFD[3.49554] → [3.78331:78341]

BF:BFD[3.78341] → [3.78342:78342]

B:BD[3.78342] → [3.78343:79872]

# pijul clone
Clone a repository into a new directory
## Usage
```cmd
pijul clone [-h | --help] [-V | --version] [ --from-branch <from_branch> ] [--patch <patch> …] [(-p | --port) <port>] [--to-branch <to_branch>] <from> [to]
```
## Description
Clone a single branch of a remote repository, i.e. initialise a new
repository, and apply all patches from a branch from the remote
repository. This is equivalent to `pijul init`, followed by `pijul
pull`.
## Example
From outside a repository:
```
pijul clone https://nest.pijul.com/pijul_org/pijul
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --from-branch \<from-branch\>
  Clone branch \<from-branch\> from the remote repository, instead of
  the default branch (which is "master").
- \<from\>
  A URI to clone. At the moment, only local paths, SSH paths (such as
  `me@example.com:path/to/repository`) and HTTP(S) URLs are supported.
- --patch \<patch\> …
  Pull patch \<patch\> and its dependencies. Can appear multiple times on the command line.
- -p \<port\>, --port \<port\>
  If the repository is accessed over SSH, the port of the remote SSH
  server, defaulting to 22 (the standard SSH port).
- --to-branch \<branch\>
  Store this branch as \<branch\> instead of using the same name as
  the remote branch.
- [to]
  Path to the local directory where the repository will be cloned,
  defaulting to the current directory followed by the basename of the
  URI in <from>.

File deletion: clone.md
BF:BFD[3.49554] → [4.19674:19684]
BF:BFD[4.19684] → [4.19685:19685]
B:BD[4.19685] → [4.19686:19831]
∅:BD[2.2141] → [4.19831:19832]
B:BD[4.19831] → [4.19831:19832]
∅:BD[2.2143] → [4.19832:19843]
B:BD[4.19832] → [4.19832:19843]
∅:BD[2.2146] → [4.19843:19854]
B:BD[4.19843] → [4.19843:19854]
B:BD[4.19854] → [2.2147:2160]
∅:BD[2.2160] → [4.19891:19892]
B:BD[4.19891] → [4.19891:19892]
B:BD[4.19892] → [2.2161:2185]
∅:BD[2.2185] → [4.19943:19944]
B:BD[4.19943] → [4.19943:19944]
B:BD[4.19944] → [2.2186:2316]
∅:BD[2.2316] → [4.20016:20030]
B:BD[4.20016] → [4.20016:20030]
∅:BD[2.2401] → [4.20030:20031]
B:BD[4.20030] → [4.20030:20031]
B:BD[4.20031] → [2.2402:2506]
∅:BD[2.2506] → [4.20149:20150]
B:BD[4.20149] → [4.20149:20150]
B:BD[4.20150] → [2.2507:2524]
∅:BD[2.2524] → [4.20194:20195]
B:BD[4.20194] → [4.20194:20195]
B:BD[4.20030] → [2.2317:2401]
B:BD[4.19843] → [2.2144:2146]
B:BD[4.19832] → [2.2142:2143]
B:BD[4.19831] → [2.2140:2141]
```
# pijul clone
Clones an existing pijul repository
##  Usage
```
pijul clone [FLAGS] [OPTIONS] <remote> [--] [path]
```
##  Args
`<remote>`
`<path>`
##  Flags
`-h, --help`
Prints help information
`--lazy`
only download changes with alive contents
`-k`
Do not check certificates
`-V, --version`
Prints version information
##  Options
set the remote channel [default: main]
`--path <partial-paths>...`
clone this path
`--state <state>`
clone this state
`--change <change>`
clone this change and its dependencies
`--channel <channel>`
```

File deletion: credit.md

BF:BFD[3.49554] → [3.77295:77306]

BF:BFD[3.77306] → [3.77307:77307]

B:BD[3.77307] → [3.77308:78330]

# pijul credit
Annotate a file with the patch that last touched each line
## Usage
```cmd
pijul credit [-h | --help] [-V | --version] [--repository <repository>] [--branch <branch>] <file>
```
## Description
Prints an annotated version of the file named `<file>` *in the
pristine* on the standard output, where each line is prefixed by the
patch that introduced it (or the last patch that modified it).
This command doesn't take the version of `<file>` in the working copy,
and only considers the pristine.
## Example
From the repository root, with a file named `Cargo.toml` in directory `pijul`:
```
pijul credit pijul/Cargo.toml
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --branch \<branch\>
  Annotate the file in branch \<branch\> instead of the current branch.
- \<file\>
  The name of the file to annotate

File deletion: credit.md
BF:BFD[3.49554] → [4.19353:19364]
BF:BFD[4.19364] → [4.19365:19365]
B:BD[4.19365] → [4.19366:19513]
∅:BD[2.2048] → [4.19513:19525]
B:BD[4.19513] → [4.19513:19525]
∅:BD[2.2063] → [4.19525:19526]
B:BD[4.19525] → [4.19525:19526]
B:BD[4.19526] → [2.2064:2088]
∅:BD[2.2088] → [4.19563:19564]
B:BD[4.19563] → [4.19563:19564]
B:BD[4.19564] → [2.2089:2133]
∅:BD[2.2133] → [4.19607:19645]
B:BD[4.19607] → [4.19607:19645]
∅:BD[2.2136] → [4.19645:19673]
B:BD[4.19645] → [4.19645:19673]
B:BD[4.19673] → [2.2137:2139]
B:BD[4.19645] → [2.2134:2136]
B:BD[4.19525] → [2.2049:2063]
B:BD[4.19513] → [2.2046:2048]
```
# pijul credit
Shows which patch last affected each line of the every file
##  Usage
```
pijul credit [OPTIONS] <file>
```
##  Args
`<file>`
##  Flags
Prints help information
`-V, --version`
Prints version information
##  Options
`--channel <channel>`
`--repository <repo-path>`
`-h, --help`
```

File deletion: diff.md

BF:BFD[3.49554] → [3.74303:74312]

BF:BFD[3.74312] → [3.74313:74313]

B:BD[3.74313] → [3.74314:75753]

# pijul diff
Show changes since the last recorded version
## Usage
```cmd
pijul diff [-h | --help] [-V | --version] [ --myers ] [ --patience ] [--repository <repository>] [--branch <branch>] [prefix…]
```
## Description
Print the difference between the pristine and the working copy, or in
other words, what would be recorded if `record` were called now.
This command can compare another branch than the current one using the
`--branch` argument, and can compare the directory or file in
`<prefix>` instead of the whole directory.
## Example
Show all the changes in the "src" and "tests" directories.
```
pijul diff src tests
```
## Options
- -h, --help
  Print a help message and exit.
- --myers
  Use [Myers' diff algorithm](../theory/diff.md). This is the default behaviour, and this flag exists for consistency only.
- --patience
  Use [Patience diff](https://en.wikipedia.org/wiki/Patience_sorting#Algorithm_for_finding_a_longest_increasing_subsequence), with Myers diff between common unique lines.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --branch \<branch\>
  Compare branch \<branch\> instead of the current branch (the default).
- [prefix…]
  A (possibly empty) list of paths in the repository to compare with
  the pristine. If empty, the whole repository is compared.

File deletion: diff.md
BF:BFD[3.49554] → [4.19000:19009]
BF:BFD[4.19009] → [4.19010:19010]
B:BD[4.19010] → [4.19011:19162]
∅:BD[2.1944] → [4.19162:19164]
B:BD[4.19162] → [4.19162:19164]
∅:BD[2.1946] → [4.19164:19175]
B:BD[4.19164] → [4.19164:19175]
B:BD[4.19175] → [2.1947:1985]
∅:BD[2.1985] → [4.19212:19223]
B:BD[4.19212] → [4.19212:19223]
∅:BD[2.1988] → [4.19223:19233]
B:BD[4.19223] → [4.19223:19233]
∅:BD[2.1991] → [4.19233:19242]
B:BD[4.19233] → [4.19233:19242]
∅:BD[2.1993] → [4.19242:19243]
B:BD[4.19242] → [4.19242:19243]
B:BD[4.19243] → [2.1994:2039]
∅:BD[2.2039] → [4.19286:19324]
B:BD[4.19286] → [4.19286:19324]
∅:BD[2.2042] → [4.19324:19352]
B:BD[4.19324] → [4.19324:19352]
B:BD[4.19352] → [2.2043:2045]
B:BD[4.19324] → [2.2040:2042]
B:BD[4.19242] → [2.1992:1993]
B:BD[4.19233] → [2.1989:1991]
B:BD[4.19223] → [2.1986:1988]
B:BD[4.19164] → [2.1945:1946]
B:BD[4.19162] → [2.1943:1944]
```
# pijul diff
Shows difference between two channels/changes
##  Usage
```
pijul diff [FLAGS] [OPTIONS] [prefixes]...
```
##  Args
`<prefixes>...`
##  Flags
`-h, --help`
Prints help information
`--json`
`--short`
`--tag`
`-V, --version`
Prints version information
##  Options
`--channel <channel>`
`--repository <repo-path>`
```

File deletion: fork.md

BF:BFD[3.49554] → [3.72248:72257]

BF:BFD[3.72257] → [3.72258:72258]

B:BD[3.72258] → [3.72259:73325]

# pijul fork
Fork a branch into a new one.
## Usage
```cmd
pijul fork [-h | --help] [-V | --version] [--repository <repository>] [--branch <branch>] <to>
```
## Description
Create a new branch with the same contents as branch `<branch>`, or as
the current branch if `--branch` is not specified.
Branches in Pijul are light, and running this command writes very few
bytes on the disk.
Note that the purpose of branches in Pijul is quite different from
Git, since Git's "feature branches" can usually be implemented by
just patches.
## Example
When initialising a repository, a branch called "master" is
created. To create its first fork, and call it "unstable", do:
```
pijul fork unstable
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --branch \<branch\>
  Fork branch \<branch\> instead of the current branch (the default).
- [to]
  Name of the new branch.

File deletion: fork.md
BF:BFD[3.49554] → [4.18707:18716]
BF:BFD[4.18716] → [4.18717:18717]
B:BD[4.18717] → [4.18718:18818]
∅:BD[2.1848] → [4.18818:18831]
B:BD[4.18818] → [4.18818:18831]
B:BD[4.18831] → [2.1849:1862]
∅:BD[2.1862] → [4.18868:18869]
B:BD[4.18868] → [4.18868:18869]
B:BD[4.18869] → [2.1863:1932]
∅:BD[2.1932] → [4.18912:18947]
B:BD[4.18912] → [4.18912:18947]
∅:BD[2.1935] → [4.18947:18970]
B:BD[4.18947] → [4.18947:18970]
∅:BD[2.1938] → [4.18970:18998]
B:BD[4.18970] → [4.18970:18998]
∅:BD[2.1940] → [4.18998:18999]
B:BD[4.18998] → [4.18998:18999]
B:BD[4.18999] → [2.1941:1942]
B:BD[4.18998] → [2.1939:1940]
B:BD[4.18970] → [2.1936:1938]
B:BD[4.18947] → [2.1933:1935]
B:BD[4.18818] → [2.1846:1848]
```
# pijul fork
Create a new channel
##  Usage
```
pijul fork [OPTIONS] <to>
```
##  Args
`<to>`
##  Flags
`-h, --help`
Prints help information
`-V, --version`
Prints version information
##  Options
`--change <change>`
`--channel <channel>`
`--repository <repo-path>`
```

File deletion: init.md

BF:BFD[3.49554] → [3.71340:71349]

BF:BFD[3.71349] → [3.71350:71350]

B:BD[3.71350] → [3.71351:71796]

# pijul init
Initialise a new repository
## Usage
```cmd
pijul init [-h | --help] [-V | --version] <directory>
```
## Description
Initialise a new repository in directory `<directory>`, if specified,
or in the current directory else.
## Example
```
pijul init
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- \<directory\>
  The directory of the new repository.

File deletion: init.md
BF:BFD[3.49554] → [4.18442:18451]
BF:BFD[4.18451] → [4.18452:18452]
B:BD[4.18452] → [4.18453:18574]
∅:BD[2.1756] → [4.18574:18576]
B:BD[4.18574] → [4.18574:18576]
∅:BD[2.1758] → [4.18576:18587]
B:BD[4.18576] → [4.18576:18587]
B:BD[4.18587] → [2.1759:1772]
∅:BD[2.1772] → [4.18624:18625]
B:BD[4.18624] → [4.18624:18625]
B:BD[4.18625] → [2.1773:1842]
∅:BD[2.1842] → [4.18668:18706]
B:BD[4.18668] → [4.18668:18706]
B:BD[4.18706] → [2.1843:1845]
B:BD[4.18576] → [2.1757:1758]
B:BD[4.18574] → [2.1755:1756]
```
# pijul init
Initializes an empty pijul repository
##  Usage
```
pijul init [OPTIONS] [path]
```
##  Args
`<path>`
##  Flags
`-h, --help`
Prints help information
`-V, --version`
Prints version information
##  Options
`--channel <channel>`
```

File deletion: log.md

BF:BFD[3.49554] → [3.68068:68076]

BF:BFD[3.68076] → [3.68077:68077]

B:BD[3.68077] → [3.68078:69810]

# pijul log
List all the patches in a branch
## Usage
```cmd
pijul log [-h | --help] [-V | --version] [ --hash-only ] [ --internal-id <internal-id>… ] [--repository <repository>] [--branch <branch>] [--grep <regex>]
```
## Description
Prints the list of all patches applied to branch `<branch>` if
`--branch` is present, or to the current branch else.  The patches are
printed in the reverse order in which they were applied to the branch,
and the information printed includes patch hashes, internal
identifiers, among others.
If desired, a restricted subset of the changes, specified by `--internal-id`, can be listed. Here, `<internal-id>` is a list of internal patch identifiers, where an internal patch identifier is of the form `tp4Jz1j2PEY`.
`--hash-only` prints a list of patches in a machine-readable format, to be exchanged when comparing patchsets between repositories.
## Example
From the repository root:
```
pijul log
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --branch \<branch\>
  Print changes on branch \<branch\> instead of the current branch.
- --hash-only
  Print the changes in binary format. This option is essentially meant
  to be used when calling this command remotely over SSH.
- --internal-id \<internal-id\>…
  Restrict the list to the set of patches specified by
  \<internal-id\>. One could for example run
  ```
  pijul log --internal-id EuTRmk0mzNk tp4Jz1j2PEY
  ```
- --grep \<regex\>
  Select only patches matching the supplied regular expression (may
  appear several times).

File deletion: log.md
BF:BFD[3.49554] → [4.18136:18144]
BF:BFD[4.18144] → [4.18145:18145]
B:BD[4.18145] → [4.18146:18267]
∅:BD[2.1655] → [4.18267:18268]
B:BD[4.18267] → [4.18267:18268]
∅:BD[2.1657] → [4.18268:18283]
B:BD[4.18268] → [4.18268:18283]
B:BD[4.18283] → [2.1658:1698]
∅:BD[2.1698] → [4.18320:18332]
B:BD[4.18320] → [4.18320:18332]
B:BD[4.18332] → [2.1699:1700]
∅:BD[2.1700] → [4.18375:18376]
B:BD[4.18375] → [4.18375:18376]
∅:BD[2.1717] → [4.18376:18377]
B:BD[4.18376] → [4.18376:18377]
∅:BD[2.1747] → [4.18377:18413]
B:BD[4.18377] → [4.18377:18413]
∅:BD[2.1750] → [4.18413:18440]
B:BD[4.18413] → [4.18413:18440]
∅:BD[2.1752] → [4.18440:18441]
B:BD[4.18440] → [4.18440:18441]
B:BD[4.18441] → [2.1753:1754]
B:BD[4.18440] → [2.1751:1752]
B:BD[4.18413] → [2.1748:1750]
B:BD[4.18377] → [2.1718:1747]
B:BD[4.18376] → [2.1701:1717]
B:BD[4.18268] → [2.1656:1657]
B:BD[4.18267] → [2.1654:1655]
```
# pijul log
Show the entire log of changes
##  Usage
```
pijul log [FLAGS] [OPTIONS]
```
##  Flags
`--description`
`--hash-only`
`-h, --help`
Prints help information
`--state`
##  Options
`--channel <channel>`
`--repository <repo-path>`
Prints version information
`-V, --version`
```

File deletion: ls.md

BF:BFD[3.49554] → [3.67356:67363]

BF:BFD[3.67363] → [3.67364:67364]

B:BD[3.67364] → [3.67365:68067]

# pijul ls
List files in the repository
## Usage
```cmd
pijul ls [-h | --help] [-V | --version] [--repository <repository>] [dir]…
```
## Description
Lists all the files in directory `<dir>`, that are currently tracked
in repository `<repository>` (or the repository in the current
directory if `--repository` is missing).
## Example
```
pijul ls src tests
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- [div]…
  List of directories to list. If this list is empty, the whole directory is listed.

File deletion: ls.md
BF:BFD[3.49554] → [4.17909:17916]
BF:BFD[4.17916] → [4.17917:17917]
B:BD[4.17917] → [4.17918:18010]
∅:BD[2.1578] → [4.18010:18011]
B:BD[4.18010] → [4.18010:18011]
B:BD[4.18011] → [2.1579:1603]
∅:BD[2.1603] → [4.18048:18049]
B:BD[4.18048] → [4.18048:18049]
B:BD[4.18049] → [2.1604:1620]
∅:BD[2.1620] → [4.18092:18093]
B:BD[4.18092] → [4.18092:18093]
∅:BD[2.1648] → [4.18093:18094]
B:BD[4.18093] → [4.18093:18094]
∅:BD[2.1650] → [4.18094:18135]
B:BD[4.18094] → [4.18094:18135]
B:BD[4.18135] → [2.1651:1653]
B:BD[4.18094] → [2.1649:1650]
B:BD[4.18093] → [2.1621:1648]
B:BD[4.18010] → [2.1564:1578]
```
# pijul ls
Lists files tracked by pijul
##  Usage
```
pijul ls [OPTIONS]
```
##  Flags
Prints help information
`-V, --version`
##  Options
`--repository <repo-path>`
Prints version information
`-h, --help`
```

File deletion: mv.md

BF:BFD[3.49554] → [3.66269:66276]

BF:BFD[3.66276] → [3.66277:66277]

B:BD[3.66277] → [3.66278:67355]

# pijul mv
Move and rename files and directories
## Usage
```cmd
pijul mv [-h | --help] [-V | --version] [--repository <repository>] <files>…
```
## Description
Move and/or rename files and directories. The files listed in
`<files>` must all be in the tree. `<files>` must contain at least two
paths.
If `<files>` contains exactly two paths, and the second path is an
existing directory, the first file or directory is moved to the second
one. If the second path is not an existing directory, the name of the
first file or directory is changed to the second one.
If `<files>` contains n > 2 paths, the last path *must* be an existing
directory, and the first n - 1 files or directories are moved to the
last path.
## Example
```
pijul mv a b
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- \<files\>…
  List of at least two paths, as explained in the description above.

File deletion: mv.md
BF:BFD[3.49554] → [4.17629:17636]
BF:BFD[4.17636] → [4.17637:17637]
B:BD[4.17637] → [4.17638:17771]
∅:BD[2.1474] → [4.17771:17773]
B:BD[4.17771] → [4.17771:17773]
∅:BD[2.1476] → [4.17773:17784]
B:BD[4.17773] → [4.17773:17784]
B:BD[4.17784] → [2.1477:1490]
∅:BD[2.1490] → [4.17821:17822]
B:BD[4.17821] → [4.17821:17822]
B:BD[4.17822] → [2.1491:1560]
∅:BD[2.1560] → [4.17865:17908]
B:BD[4.17865] → [4.17865:17908]
B:BD[4.17908] → [2.1561:1563]
B:BD[4.17773] → [2.1475:1476]
B:BD[4.17771] → [2.1473:1474]
```
# pijul mv
Moves a file in the working copy and the tree
##  Usage
```
pijul mv [OPTIONS] [paths]...
```
##  Args
`<paths>...`
##  Flags
`-h, --help`
Prints help information
`-V, --version`
Prints version information
##  Options
`--repository <repo-path>`
```

File deletion: pull.md

BF:BFD[3.49554] → [3.61545:61554]

BF:BFD[3.61554] → [3.61555:61555]

B:BD[3.61555] → [3.61556:64494]

# pijul pull
Pull a patch from a remote repository
## Usage
```cmd
pijul pull [-h | --help] [-V | --version] [--repository <repository>] [--from-branch <from_branch>] [(-p | --port) <port>] [--to-branch <to_branch>] [--set-remote <set-remote>] [--set-default] [-a | --all] [remote]
```
## Description
Pull patches from a remote repository to a branch of a local
repository to a branch. Patch selection is either interactive, or
includes all patches in the current branch if `-a` (or `--all`) is
present.
If the `<to_branch>` does not exist in the local repository, it will
be created. If the `<from_branch>` does not exist in the remote
repository, this command does nothing.
This command can also save remote repositories, in two different ways:
- If `--set-default` is specified, the remote destination becomes the
  default destination, and it is not necessary to give it a
  name. Subsequent pulls to the same address can be done by simply
  running `pijul pull`.
  It is not necessary to give a name (using `--set-remote`) to the
  default destination, although it is possible.
- If `--set-remote` is specified, the remote destination is saved as
  `<set-remote>`, and can be reused in subsequent commands. For
  example, after calling `pijul pull me@nest.pijul.com:example
  --set-remote nest`, pulling from the same address
  (me@nest.pijul.com:example) again can be done by running
  `pijul pull nest`.
Saved remote repositories are written to ".pijul/meta.toml" (at the
root of the repository).
## Examples
```
pijul pull me@nest.pijul.com:example --set-remote nest
pijul pull nest -a
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --from-branch \<from-branch\>
  Pull patches from branch \<from-branch\> in the remote repository,
  instead of the default branch ("master").
- -p \<port\>, --port \<port\>
  If the remote repository is accessed over SSH, the port of the
  remote SSH server, defaulting to 22 (the standard SSH port).
- --to-branch \<to-branch\>
  Pull patches to branch \<to-branch\> in the local repository,
  instead of the current branch.
- --set-remote \<set-remote\>
  Save this remote repository as \<set-remote\>. In subsequent
  commands, name \<set-remote\> can be used instead of this URI.
- --set-default
  Make this remote repository the default. If subsequent commands
  involving remote repositories are called without a URI, the default
  remote repository will be used as the URI.
- -a, --all
  Don't select patches to pull interactively, pull all patches
  instead.
- [remote]
  Name or URI of the remote repository. A name can be for instance
  "nest", while a URI can be a HTTP or HTTPS URL, or an SSH address
  (such as "me@nest.pijul.com:repository"), or a local path.

File deletion: pull.md
BF:BFD[3.49554] → [4.17081:17090]
BF:BFD[4.17090] → [4.17091:17091]
B:BD[4.17091] → [4.17092:17238]
∅:BD[2.1153] → [4.17238:17239]
B:BD[4.17238] → [4.17238:17239]
B:BD[4.17239] → [2.1154:1242]
∅:BD[2.1242] → [4.17325:17351]
B:BD[4.17325] → [4.17325:17351]
B:BD[4.17351] → [2.1243:1341]
∅:BD[2.1341] → [4.17407:17408]
B:BD[4.17407] → [4.17407:17408]
B:BD[4.17408] → [2.1342:1391]
∅:BD[2.1391] → [4.17445:17446]
B:BD[4.17445] → [4.17445:17446]
B:BD[4.17446] → [2.1392:1419]
∅:BD[2.1419] → [4.17518:17532]
B:BD[4.17518] → [4.17518:17532]
∅:BD[2.1443] → [4.17532:17533]
B:BD[4.17532] → [4.17532:17533]
B:BD[4.17533] → [2.1444:1446]
∅:BD[2.1446] → [4.17553:17586]
B:BD[4.17553] → [4.17553:17586]
B:BD[4.17586] → [2.1447:1468]
∅:BD[2.1468] → [4.17600:17627]
B:BD[4.17600] → [4.17600:17627]
∅:BD[2.1470] → [4.17627:17628]
B:BD[4.17627] → [4.17627:17628]
B:BD[4.17628] → [2.1471:1472]
B:BD[4.17627] → [2.1469:1470]
B:BD[4.17532] → [2.1420:1443]
B:BD[4.17238] → [2.1152:1153]
```
# pijul pull
Pulls changes from a remote upstream
##  Usage
```
pijul pull [FLAGS] [OPTIONS] [from] [-- <changes>...]
```
##  Args
`<from>`
`<changes>...`
Pull changes from the local repository, not necessarily from a channel
##  Flags
`-a, --all`
`--full`
Download full changes, even when not necessary
`-h, --help`
Prints help information
`-k`
Do not check certificates
`-V, --version`
Prints version information
##  Options
`--from-channel <from-channel>`
`--path <path>`
`--repository <repo-path>`
`--channel <channel>`
```

File deletion: push.md

BF:BFD[3.49554] → [3.58371:58380]

BF:BFD[3.58380] → [3.58381:58381]

B:BD[3.58381] → [3.58382:61544]

# pijul push
Push a patch to a remote repository
## Usage
```cmd
pijul push [-h | --help] [-V | --version] [--repository <repository>] [--from-branch <from_branch>] [(-p | --port) <port>] [--to-branch <to_branch>] [--set-remote <set-remote>] [--set-default] [-a | --all] [--force] [remote]
```
## Description
Push patches from a branch of a local repository to a branch of a
remote repository. Patch selection is either interactive, or includes
all patches in the current branch if `-a` (or `--all`) is present.
If the `<to_branch>` does not exist in the remote repository, it will
be created. If the `<from_branch>` does not exist in the local
repository, this command does nothing.
This command can also save remote repositories, in two different ways:
- If `--set-default` is specified, the remote destination becomes the
  default destination, and it is not necessary to give it a
  name. Subsequent pushes to the same address can be done by simply
  running `pijul push`.
  It is not necessary to give a name (using `--set-remote`) to the
  default destination, although it is possible.
- If `--set-remote` is specified, the remote destination is saved as
  `<set-remote>`, and can be reused in subsequent commands. For
  example, after calling `pijul push me@nest.pijul.com:example
  --set-remote nest`, pushing to the same address
  (me@nest.pijul.com:example) again can be done by running
  `pijul push nest`.
Saved remote repositories are written to ".pijul/meta.toml" (at the
root of the repository).
Finally, push refuses to apply patches to the remote side if the
remote side has patches not in the local branch. This behaviour can be
overriden with `--force`.
## Examples
```
pijul push me@nest.pijul.com:example --set-remote nest
pijul push nest
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --from-branch \<from-branch\>
  Push patches from branch \<from-branch\> in the local repository,
  instead of the current branch (the default).
- -p \<port\>, --port \<port\>
  If the remote repository is accessed over SSH, the port of the
  remote SSH server, defaulting to 22 (the standard SSH port).
- --to-branch \<to-branch\>
  Push patches to branch \<to-branch\> in the remote repository,
  instead of the default branch ("master").
- --set-remote \<set-remote\>
  Save this remote repository as \<set-remote\>. In subsequent
  commands, name \<set-remote\> can be used instead of this URI.
- --set-default
  Make this remote repository the default. If subsequent commands
  involving remote repositories are called without a URI, the default
  remote repository will be used as the URI.
- -a, --all
  Don't select patches to push interactively, push all patches
  instead.
- --force
  Force a non-fast-forward push.
- [remote]
  Name or URI of the remote repository. A name can be for instance
  "nest", while a URI can be a HTTP or HTTPS URL, or an SSH address
  (such as "me@nest.pijul.com:repository"), or a local path.

File deletion: push.md
BF:BFD[3.49554] → [4.16646:16655]
BF:BFD[4.16655] → [4.16656:16656]
B:BD[4.16656] → [4.16657:16790]
∅:BD[2.958] → [4.16790:16791]
B:BD[4.16790] → [4.16790:16791]
B:BD[4.16791] → [2.959:1001]
∅:BD[2.1001] → [4.16835:16860]
B:BD[4.16835] → [4.16835:16860]
∅:BD[2.1003] → [4.16860:16861]
B:BD[4.16860] → [4.16860:16861]
B:BD[4.16861] → [2.1004:1093]
∅:BD[2.1093] → [4.16898:16899]
B:BD[4.16898] → [4.16898:16899]
B:BD[4.16899] → [2.1094:1121]
∅:BD[2.1121] → [4.16971:17008]
B:BD[4.16971] → [4.16971:17008]
∅:BD[2.1124] → [4.17008:17009]
B:BD[4.17008] → [4.17008:17009]
B:BD[4.17009] → [2.1125:1144]
∅:BD[2.1144] → [4.17023:17050]
B:BD[4.17023] → [4.17023:17050]
∅:BD[2.1147] → [4.17050:17079]
B:BD[4.17050] → [4.17050:17079]
∅:BD[2.1149] → [4.17079:17080]
B:BD[4.17079] → [4.17079:17080]
B:BD[4.17080] → [2.1150:1151]
B:BD[4.17079] → [2.1148:1149]
B:BD[4.17050] → [2.1145:1147]
B:BD[4.17008] → [2.1122:1124]
B:BD[4.16860] → [2.1002:1003]
B:BD[4.16790] → [2.950:958]
```
# pijul push
Pushes changes to a remote upstream
##  Usage
```
pijul push [FLAGS] [OPTIONS] [to] [-- <changes>...]
```
##  Args
`<changes>...`
Push only these changes
##  Flags
`-a, --all`
`-h, --help`
Prints help information
`-k`
Do not check certificates
`-V, --version`
Prints version information
##  Options
`--channel <channel>`
`--path <path>`
`--repository <repo-path>`
`--to-channel <to-channel>`
`<to>`
```

File deletion: record.md

BF:BFD[3.49554] → [3.55653:55664]

BF:BFD[3.55664] → [3.55665:55665]

B:BD[3.55665] → [3.55666:58370]

# pijul record
Record the changes in the working copy, creating a patch
## Usage
```cmd
pijul record [-h | --help] [-V | --version] [--repository <repository>] [--branch <branch>] [(-A | --author) <author>] [(-m | --message) <message>] [--depends-on <depends-on>…] [-a | --all] [prefix]…
```
## Description
Record is the only command for creating patches in Pijul.
This command compares the pristine with the working copy, creates a
patch, applies it to the pristine, and synchronises file moves.
A patch is then saved to .pijul/patches (from the root of the
repository), and can later be exchanged with
[push](./reference/push.html) and [pull](./reference/pull.html).
By default, the comparison happens between the whole pristine and the
whole working copy. It can also be restricted to a list of paths,
specified as `[prefix]`.
If this is the first command to be run after installing Pijul for the
first time, a file named ~/.pijulconfig/config.toml will be created, and
your author name will be saved there.
When using Pijul, it is highly recommended to sign your
patches. Record automatically does this after [keys have been
setup](./signing_patches.html).
## Interative use
When `pijul record` is invoked interactively, the user will be asked a
series of questions with the prompt `[ynkad]`. The possible answers are:
* `y`: include the change in the patch.
* `n`: don't include the change in the patch.
* `k`: undo the previous answer and go back to the previous change.
* `a`: include all the following changes in the patch.
* `d`: do not include any of the following changes in the patch.
## Examples
```
pijul record -a -m "My first patch" -A "me <me@example.com>" src
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in
  \<repository\> instead.
- --branch \<branch\>
  Compare branch \<branch\>, instead of the current branch, with the
  working copy.
- -A, --author
  Set the patch's author. By default, the first patch you create on
  any repository after installing Pijul saves your author name in
  "~/.pijulconfig/config.toml".
- -m, --message
  Add a message to this patch, summarising your changes.
- --depends-on \<depends-on\>
  Add a list of dependencies to this patch. Dependencies are normally
  inferred by Pijul, but some semantic dependencies cannot be
  inferred. Use this command to add them.
- -a, --all
  Don't select patches to push interactively, push all patches
  instead.
- [prefix]…
  Restrict the comparison to a list of paths instead of comparing the
  whole repository.

File deletion: record.md
BF:BFD[3.49554] → [4.16215:16226]
BF:BFD[4.16226] → [4.16227:16227]
B:BD[4.16227] → [4.16228:16358]
∅:BD[2.807] → [4.16358:16360]
B:BD[4.16358] → [4.16358:16360]
∅:BD[2.809] → [4.16360:16384]
B:BD[4.16360] → [4.16360:16384]
B:BD[4.16384] → [2.810:825]
∅:BD[2.825] → [4.16421:16422]
B:BD[4.16421] → [4.16421:16422]
B:BD[4.16422] → [2.826:859]
∅:BD[2.859] → [4.16425:16436]
B:BD[4.16425] → [4.16425:16436]
∅:BD[2.862] → [4.16436:16445]
B:BD[4.16436] → [4.16436:16445]
B:BD[4.16445] → [2.863:881]
∅:BD[2.881] → [4.16488:16489]
B:BD[4.16488] → [4.16488:16489]
∅:BD[2.909] → [4.16489:16490]
B:BD[4.16489] → [4.16489:16490]
∅:BD[2.911] → [4.16490:16503]
B:BD[4.16490] → [4.16490:16503]
B:BD[4.16503] → [2.912:933]
∅:BD[2.933] → [4.16519:16539]
B:BD[4.16519] → [4.16519:16539]
∅:BD[2.936] → [4.16539:16563]
B:BD[4.16539] → [4.16539:16563]
∅:BD[2.939] → [4.16563:16590]
B:BD[4.16563] → [4.16563:16590]
∅:BD[2.942] → [4.16590:16618]
B:BD[4.16590] → [4.16590:16618]
∅:BD[2.945] → [4.16618:16644]
B:BD[4.16618] → [4.16618:16644]
∅:BD[2.947] → [4.16644:16645]
B:BD[4.16644] → [4.16644:16645]
B:BD[4.16645] → [2.948:949]
B:BD[4.16644] → [2.946:947]
B:BD[4.16618] → [2.943:945]
B:BD[4.16590] → [2.940:942]
B:BD[4.16563] → [2.937:939]
B:BD[4.16539] → [2.934:936]
B:BD[4.16490] → [2.910:911]
B:BD[4.16489] → [2.882:909]
B:BD[4.16436] → [2.860:862]
B:BD[4.16360] → [2.808:809]
B:BD[4.16358] → [2.806:807]
```
# pijul record
Creates a new change
##  Usage
```
pijul record [FLAGS] [OPTIONS] [prefixes]...
```
##  Args
`<prefixes>...`
##  Flags
`-a, --all`
`-h, --help`
Prints help information
`-S`
`--stdin`
`--tag`
`-V, --version`
##  Options
`--amend <amend>`
`--author <author>`
`--channel <channel>`
`-m, --message <message>`
`--repository <repo-path>`
`--timestamp <timestamp>`
Prints version information
```
File deletion: remote
BF:BFD[3.49554] → [3.54333:54341]
BF:BFD[3.54341] → [3.54342:54342]
File deletion: delete.md
BF:BFD[3.54342] → [3.54721:54732]
BF:BFD[3.54732] → [3.54733:54733]
B:BD[3.54733] → [3.54734:54757]
B:BD[3.54757] → [4.16057:16067]
∅:BD[4.16067] → [3.54823:54824]
B:BD[3.54823] → [3.54823:54824]
B:BD[3.54833] → [3.54833:54838]
B:BD[3.54838] → [4.16068:16097]
∅:BD[4.16097] → [3.54896:54901]
B:BD[3.54896] → [3.54896:54901]
B:BD[3.54901] → [4.16098:16120]
B:BD[4.16120] → [2.717:718]
∅:BD[2.718] → [3.54919:54920]
∅:BD[4.16120] → [3.54919:54920]
B:BD[3.54919] → [3.54919:54920]
B:BD[3.54920] → [4.16121:16122]
∅:BD[2.720] → [4.16122:16133]
B:BD[4.16122] → [4.16122:16133]
B:BD[4.16133] → [2.721:734]
∅:BD[2.734] → [3.54955:54956]
∅:BD[4.16170] → [3.54955:54956]
B:BD[3.54955] → [3.54955:54956]
B:BD[3.54956] → [2.735:759]
∅:BD[2.759] → [3.54956:54957]
∅:BD[4.16214] → [3.54956:54957]
B:BD[3.54956] → [3.54956:54957]
B:BD[3.54957] → [2.760:805]
B:BD[4.16122] → [2.719:720]
```
# pijul remote delete
##  Usage
```
pijul remote delete <remote>
```
##  Args
`<remote>`
##  Flags
`-h, --help`
Prints help information
`-V, --version`
Prints version information
```

File deletion: remote.md

BF:BFD[3.49554] → [3.53848:53859]

BF:BFD[3.53859] → [3.53860:53860]

B:BD[3.53860] → [3.53861:54332]

# pijul remote
View and modify saved remote repositories.
## Usage
```
pijul remote [-h | --help] [-V | --version] [SUBCOMMAND]
```
## Description
Pijul can save remote repositories under names for easy usage. The remote
command can show and update the names for remote repositories.
## Subcommands
- **default:** sets the default remote to be used
- **delete:** remotes the name for the remote
- **list:** lists current remotes
- **set:** adds or updates a remote

File deletion: remote.md

BF:BFD[3.49554] → [4.15711:15722]

BF:BFD[4.15722] → [4.15723:15723]

B:BD[4.15723] → [4.15724:16056]

# pijul remote
Manages remote repositories
##  Usage
```
pijul remote [OPTIONS] [SUBCOMMAND]
```
##  Flags
`-h, --help Prints help information`
`-V, --version Prints version information`
##  Options
`--repository <repo-path>`
##  Subcommands
`delete`
`help Prints this message or the help of the given subcommand(s)`

File deletion: remote.md

BF:BFD[3.49554] → [2.364:375]

BF:BFD[2.375] → [2.376:376]

B:BD[2.376] → [2.377:716]

# pijul remote
Manages remote repositories
##  Usage
```
pijul remote [OPTIONS] [SUBCOMMAND]
```
##  Flags
`-h, --help`
Prints help information
`-V, --version`
Prints version information
##  Options
`--repository <repo-path>`
##  Subcommands
`delete`
`help`
Prints this message or the help of the given subcommand(s)

File deletion: remove.md

BF:BFD[3.49554] → [3.53121:53132]

BF:BFD[3.53132] → [3.53133:53133]

B:BD[3.53133] → [3.53134:53847]

# pijul remove
Stop tracking a file (does *not* delete the file from the filesystem).
## Usage
```
pijul remove [-h | --help] [-V | --version] [--repository <repository>] <files>…
```
## Description
Removes files from the tree. This does not remove files from the local
filesystem. However, a patch removing a file will delete it from
remote repositories when pushing or pulling.
## Example
```
pijul mv a b
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- \<files\>…
  List of files to remove from the tree.

File deletion: remove.md
BF:BFD[3.49554] → [4.15423:15434]
BF:BFD[4.15434] → [4.15435:15435]
B:BD[4.15435] → [4.15436:15573]
∅:BD[2.274] → [4.15573:15575]
B:BD[4.15573] → [4.15573:15575]
∅:BD[2.276] → [4.15575:15586]
B:BD[4.15575] → [4.15575:15586]
B:BD[4.15586] → [2.277:290]
∅:BD[2.290] → [4.15623:15624]
B:BD[4.15623] → [4.15623:15624]
B:BD[4.15624] → [2.291:360]
∅:BD[2.360] → [4.15667:15710]
B:BD[4.15667] → [4.15667:15710]
B:BD[4.15710] → [2.361:363]
B:BD[4.15575] → [2.275:276]
B:BD[4.15573] → [2.273:274]
```
# pijul remove
Removes a file from the tree and prestine
##  Usage
```
pijul remove [OPTIONS] [paths]...
```
##  Args
`<paths>...`
##  Flags
`-h, --help`
Prints help information
`-V, --version`
Prints version information
##  Options
`--repository <repo-path>`
```
File deletion: reset.md
BF:BFD[3.49554] → [4.15072:15082]
BF:BFD[4.15082] → [4.15083:15083]
B:BD[4.15083] → [4.15084:15228]
∅:BD[2.172] → [4.15228:15230]
B:BD[4.15228] → [4.15228:15230]
∅:BD[2.174] → [4.15230:15254]
B:BD[4.15230] → [4.15230:15254]
B:BD[4.15254] → [2.175:190]
∅:BD[2.190] → [4.15291:15292]
B:BD[4.15291] → [4.15291:15292]
B:BD[4.15292] → [2.191:232]
∅:BD[2.232] → [4.15335:15336]
B:BD[4.15335] → [4.15335:15336]
∅:BD[2.260] → [4.15336:15337]
B:BD[4.15336] → [4.15336:15337]
∅:BD[2.262] → [4.15337:15371]
B:BD[4.15337] → [4.15337:15371]
∅:BD[2.265] → [4.15371:15394]
B:BD[4.15371] → [4.15371:15394]
∅:BD[2.268] → [4.15394:15421]
B:BD[4.15394] → [4.15394:15421]
∅:BD[2.270] → [4.15421:15422]
B:BD[4.15421] → [4.15421:15422]
B:BD[4.15422] → [2.271:272]
B:BD[4.15421] → [2.269:270]
B:BD[4.15394] → [2.266:268]
B:BD[4.15371] → [2.263:265]
B:BD[4.15337] → [2.261:262]
B:BD[4.15336] → [2.233:260]
B:BD[4.15230] → [2.173:174]
B:BD[4.15228] → [2.171:172]
```
# pijul reset
Reverts the working copy to the given Hash
##  Usage
```
pijul reset [FLAGS] [OPTIONS] [files]...
```
##  Args
`<files>...`
##  Flags
`--dry-run`
`-h, --help`
Prints help information
`-V, --version`
##  Options
`--change <change>`
`--channel <channel>`
`--repository <repo-path>`
Prints version information
```

File deletion: unrecord.md

BF:BFD[3.49554] → [3.49555:49568]

BF:BFD[3.49568] → [3.49569:49569]

B:BD[3.49569] → [3.49570:50778]

# pijul unrecord
Unapplies a patch from a branch.
## Usage
```cmd
pijul unrecord [-h | --help] [-V | --version] [--repository <repository>] [--branch <branch>] <patch>…
```
## Description
Unapplies a patch from a branch of the pristine (defaulting to the
current branch if `--branch` is absent). After calling this command,
running `pijul record` on the same branch will ask to create the same
patch again.
This is an essential tool to undo mistakes, and has a variety of other
uses. It is used internally to merge remote patches with unrecorded
changes when pulling and pushing, for instance.
## Example
```
pijul unrecord AfcVxwCRgKbf-aCS0wOuXAekoRNl9xIGM-_0A_KzgZPEZ_55-5klp15WWTjFRtLVDlacWDAas11yrROdlyU11i8
```
## Options
- -h, --help
  Print a help message and exit.
- -V, --version
  Print the version of Pijul and exit.
- --repository \<repository\>
  Don't run this command in the current directory, run it in \<repository\> instead.
- --branch \<branch\>
  Unrecord on branch \<branch\> instead of the current branch (the default).
- \<patch\>…
  A list of patch hashes to unrecord. Pijul will ask interactively
  which patches to unrecord if and only if this list is empty.

File deletion: unrecord.md
BF:BFD[3.49554] → [4.14686:14699]
BF:BFD[4.14699] → [4.14700:14700]
B:BD[4.14700] → [4.14701:14833]
B:BD[4.14833] → [2.0:79]
∅:BD[2.79] → [4.14911:14924]
B:BD[4.14911] → [4.14911:14924]
B:BD[4.14924] → [2.80:93]
∅:BD[2.93] → [4.14961:14962]
B:BD[4.14961] → [4.14961:14962]
B:BD[4.14962] → [2.94:163]
∅:BD[2.163] → [4.15005:15042]
B:BD[4.15005] → [4.15005:15042]
∅:BD[2.166] → [4.15042:15070]
B:BD[4.15042] → [4.15042:15070]
∅:BD[2.168] → [4.15070:15071]
B:BD[4.15070] → [4.15070:15071]
B:BD[4.15071] → [2.169:170]
B:BD[4.15070] → [2.167:168]
B:BD[4.15042] → [2.164:166]
```
# pijul unrecord
Unrecords all changes upto the given hash
##  Usage
```
pijul unrecord [OPTIONS] [change-id]...
```
##  Args
`<change-id>...`
identifier of the change (unambiguous prefixes are accepted)
##  Flags
`-h, --help`
Prints help information
`-V, --version`
Prints version information
##  Options
`--channel <channel>`
`--repository <repo-path>`
```

Delete auto-generated files, now that this is taken care of in the deployment scripts

Dependencies

In channels

Change contents

File deletion: add.md

File deletion: add.md

File deletion: apply.md

File deletion: apply.md

File deletion: archive.md

File deletion: change.md

File deletion: channel.md

File deletion: clone.md

File deletion: clone.md

File deletion: credit.md

File deletion: credit.md

File deletion: diff.md

File deletion: diff.md

File deletion: fork.md

File deletion: fork.md

File deletion: init.md

File deletion: init.md

File deletion: log.md

File deletion: log.md

File deletion: ls.md

File deletion: ls.md

File deletion: mv.md

File deletion: mv.md

File deletion: pull.md

File deletion: pull.md

File deletion: push.md

File deletion: push.md

File deletion: record.md

File deletion: record.md

File deletion: remote

File deletion: delete.md

File deletion: remote.md

File deletion: remote.md

File deletion: remote.md

File deletion: remove.md

File deletion: remove.md

File deletion: reset.md

File deletion: unrecord.md

File deletion: unrecord.md