Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@inwind.it>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 5/7][V2] btrfs-progs:  The man/btrfs.8.in man page is auto-generated
Date: Tue, 08 Nov 2011 23:12:25 +0100	[thread overview]
Message-ID: <2497663.IDYgb5Sg8s@venice> (raw)

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]



Warn that the man/btrfs.8.in man page is auto-generated

Signed off by: Goffredo Baroncelli <kreijack@inwind.it>
---
 btrfs.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/btrfs.c b/btrfs.c
index 26bd4f6..d6c840e 100644
--- a/btrfs.c
+++ b/btrfs.c
@@ -88,6 +88,11 @@
  * .\"
  * .\" Man page for the "btrfs" tool 
  * .\"
+ * .\" WARNING
+ * .\" WARNING This file is generated automatically. Don't edit, your change
+ * .\" WARNING will be lost. See the file btrfs.c for further information
+ * .\" WARNING 
+ * .\"
  * .SH NAME
  * btrfs \- control a btrfs filesystem
  ****/
-- 
1.7.7.2

-- 
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E  C054 BF04 F161 3DC5 0512

[-- Attachment #2: send-via-kmail-attach-27106-1320789397-5248.msg --]
[-- Type: text/x-patch, Size: 430 bytes --]

diff --git a/btrfs.c b/btrfs.c
index 26bd4f6..d6c840e 100644
--- a/btrfs.c
+++ b/btrfs.c
@@ -88,6 +88,11 @@
  * .\"
  * .\" Man page for the "btrfs" tool 
  * .\"
+ * .\" WARNING
+ * .\" WARNING This file is generated automatically. Don't edit, your change
+ * .\" WARNING will be lost. See the file btrfs.c for further information
+ * .\" WARNING 
+ * .\"
  * .SH NAME
  * btrfs \- control a btrfs filesystem
  ****/
-- 
1.7.7.2

                 reply	other threads:[~2011-11-08 22:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2497663.IDYgb5Sg8s@venice \
    --to=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox