Skip to content

Commit 65820cd

Browse files
committed
update man page
1 parent 2c3a107 commit 65820cd

2 files changed

Lines changed: 4 additions & 3 deletions

File tree

man/aptly.1

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ aptly looks for configuration file first in \fB~/\.aptly\.conf\fR then in \fB/us
3131
With aptly version 1\.6\.0, yaml configuration with inline documentation is supported and recommended (see \fBdebian/aptly\.conf\fR)\.
3232
.
3333
.P
34-
The legacy json configuration is still supported:
34+
The legacy json configuration is still supported (and also supports comments):
3535
.
3636
.IP "" 4
3737
.

man/aptly.1.ronn.tmpl

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,10 @@ aptly has integrated help that matches contents of this manual page, to get help
2121
aptly looks for configuration file first in `~/.aptly.conf` then in `/usr/local/etc/aptly.conf` and `/etc/aptly.conf`. If no config file found (or they are not readable), a new one is created in the
2222
home directory. If `-config=` flag is specified, aptly would use config file at specified location. Also aptly needs root directory for database, package and published repository storage. If not specified, directory defaults to `~/.aptly/`, it will be created if missing.
2323

24-
With aptly version 1.6.0, yaml configuration with inline documentation is supported and recommended (see `debian/aptly.conf`).
24+
With aptly version 1.6.0, yaml configuration with inline documentation is
25+
supported and recommended (see `debian/aptly.conf`).
2526

26-
The legacy json configuration is still supported:
27+
The legacy json configuration is still supported (and also supports comments):
2728

2829
// vim: : filetype=json
2930
// json configuration file with comments

0 commit comments

Comments
 (0)