From 53441303eaac575329e7bf4d62a5ec845452f6de Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Sun, 6 May 2007 17:50:22 +0000 Subject: [PATCH] (Create Tags Table): Clean up previous change. --- man/ChangeLog | 4 ++++ man/maintaining.texi | 8 ++++---- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/man/ChangeLog b/man/ChangeLog index ee19a3254be..8a5eb243616 100644 --- a/man/ChangeLog +++ b/man/ChangeLog @@ -1,3 +1,7 @@ +2007-05-06 Richard Stallman + + * maintaining.texi (Create Tags Table): Clean up previous change. + 2007-05-05 Francesco Potort,Al(B * maintaining.texi (Create Tags Table): Add text about the dangers of diff --git a/man/maintaining.texi b/man/maintaining.texi index ab98dccd350..c9e77ede2a1 100644 --- a/man/maintaining.texi +++ b/man/maintaining.texi @@ -409,10 +409,10 @@ source files, and the tags file will still refer correctly to the source files. If the tags file is in @file{/dev}, however, the file names are made relative to the current working directory. This is useful, for example, when writing the tags to @file{/dev/stdout}. - - Notice that, in the usual case of using relative file names, you -should not use a symbolic link pointing to a tags file in a different -directory, because this would generally render the file names invalid. + + When using a a relative file name, it should not be a symbolic link +pointing to a tags file in a different directory, because this would +generally render the file names invalid. If you specify absolute file names as arguments to @code{etags}, then the tags file will contain absolute file names. This way, the tags file -- 2.39.2