git-annex/doc/git-annex-lock.mdwn

# NAME

git-annex lock - undo unlock command

# SYNOPSIS

git annex lock `[path ...]`

# DESCRIPTION

Use this to undo an unlock command if you don't want to modify
the files any longer, or have made modifications you want to discard.

# OPTIONS

* file matching options
 
  The [[git-annex-matching-options]](1)
  can be used to specify files to lock.

* `--json`

  Enable JSON output. This is intended to be parsed by programs that use
  git-annex. Each line of output is a JSON object.

# SEE ALSO

[[git-annex]](1)

[[git-annex-add]](1)

[[git-annex-unlock]](1)

# AUTHOR

Joey Hess <id@joeyh.name>

Warning: Automatically converted into a man page by mdwn2man. Edit with care.
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# NAME`

Various typo fixes in doc/.mdwn One of my for f in `ls .mdwn \| sort -R`; do aspell -c $f; sleep 2; done sessions. 3647f704-e510-11e4-bf50-000df06acc56 2015-04-17 14:42:16 +00:00			`git-annex lock - undo unlock command`
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00
			`# SYNOPSIS`

			git annex lock `[path ...]`

			`# DESCRIPTION`

			`Use this to undo an unlock command if you don't want to modify`
v6 git-annex unlock Note that the implementation uses replaceFile, so that the actual replacement of the work tree file is atomic. This seems a good property to have! It would be possible for unlock in v6 mode to be run on files that do not have their content present. However, that would be a behavior change from before, and I don't see any immediate need to support it, so I didn't implement it. 2015-12-10 20:12:05 +00:00			`the files any longer, or have made modifications you want to discard.`
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00
			`# OPTIONS`

			`* file matching options`

			`The [[git-annex-matching-options]](1)`
			`can be used to specify files to lock.`

unlock, lock: Support --json. 2017-10-30 18:44:11 +00:00			* `--json`

			`Enable JSON output. This is intended to be parsed by programs that use`
			`git-annex. Each line of output is a JSON object.`

splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# SEE ALSO`

			`[[git-annex]](1)`

expand manpages cross-references significantly i found that most man pages only had references to the main git-annex manpage, which i stillfind pretty huge and hard to navigate through. i tried to sift through all the man pages and add cross-references between relevant pages. my general rule of thumb is that links should be both ways unless one of the pages is a more general page that would become ridiculously huge if all backlinks would be added (git-annex-preferred-content comes to mind). i have also make the links one per line as this is how it was done in the metadata pages so far. i did everything but the plumbing, utility and test commands, although some of those are linked from the other commands so cross-links were added there as well. 2015-05-29 16:12:55 +00:00			`[[git-annex-add]](1)`

			`[[git-annex-unlock]](1)`

splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# AUTHOR`

			`Joey Hess <id@joeyh.name>`

			`Warning: Automatically converted into a man page by mdwn2man. Edit with care.`