[pkgsrc/trunk]: pkgsrc/doc/guide guide: Note that "make regen" will commit th...

[gdt <gdt%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/1ede0e0e0aea
branches:  trunk
changeset: 449321:1ede0e0e0aea
user:      gdt <gdt%pkgsrc.org@localhost>
date:      Fri Mar 26 17:44:56 2021 +0000

description:
guide: Note that "make regen" will commit the new versions

It seemed obvious to me that regen would create the files, so they
could be reviewed, and that one would then commit them manually.  Warn
the next person...

diffstat:

 doc/guide/Makefile |  3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diffs (17 lines):

diff -r cb5d176f0fcc -r 1ede0e0e0aea doc/guide/Makefile
--- a/doc/guide/Makefile        Fri Mar 26 17:43:20 2021 +0000
+++ b/doc/guide/Makefile        Fri Mar 26 17:44:56 2021 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.69 2021/01/10 14:50:06 leot Exp $
+# $NetBSD: Makefile,v 1.70 2021/03/26 17:44:56 gdt Exp $
 
 DISTNAME=              pkgsrc-guide-${PKGVERSION}
 CATEGORIES=            # empty
@@ -11,6 +11,7 @@
 
 # To regenerate pkgsrc/doc/pkgsrc.{html,txt} and
 # htdocs/docs/pkgsrc, just run "make regen".
+# NOTE THAT THIS WILL COMMIT THOSE UPDATED VERSIONS!
 
 PKGVERSION!=           date '+%Y%m%d'
 DIST_SUBDIR=           ${PKGBASE}