Bug#308258: marked as done (vim: 'set secure' isn't for own files; docs misleading.)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jun 2007 21:26:02 +0100
with message-id <20070617202602.GA23075 at jamessan.com>
and subject line Bug#308258: vim: 'set secure' isn't for own files; docs misleading.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

-------------- next part --------------
An embedded message was scrubbed...
From: Adrian Irving-Beer <wisq-deb at wisq.net>
Subject: vim: 'set secure' isn't for own files; docs misleading.
Date: Sun, 08 May 2005 21:07:44 -0400
Size: 3382
Url: http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20070617/eb29135f/attachment-0002.eml 
-------------- next part --------------
An embedded message was scrubbed...
From: James Vega <jamessan at debian.org>
Subject: Re: Bug#308258: vim: 'set secure' isn't for own files; docs misleading.
Date: Sun, 17 Jun 2007 21:26:02 +0100
Size: 4468
Url: http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20070617/eb29135f/attachment-0003.eml