OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Ralf S. Engelschall
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-src                      Date:   02-Dec-2007 08:45:26
  Branch: HEAD                             Handle: 2007120207452500

  Modified files:
    openpkg-src/vim         vim.spec

  Log:
    upgrading package: vim 7.1.164 -> 7.1.166

  Summary:
    Revision    Changes     Path
    1.571       +4  -2      openpkg-src/vim/vim.spec
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-src/vim/vim.spec
  ============================================================================
  $ cvs diff -u -r1.570 -r1.571 vim.spec
  --- openpkg-src/vim/vim.spec  1 Dec 2007 09:31:38 -0000       1.570
  +++ openpkg-src/vim/vim.spec  2 Dec 2007 07:45:25 -0000       1.571
  @@ -25,7 +25,7 @@
   #   package versions
   %define       V_vl  7.1
   %define       V_vs  71
  -%define       V_pl  164
  +%define       V_pl  166
   
   #   package information
   Name:         vim
  @@ -38,7 +38,7 @@
   Group:        Editor
   License:      Charityware
   Version:      %{V_vl}.%{V_pl}
  -Release:      20071201
  +Release:      20071202
   
   #   package options
   %option       with_x11        no
  @@ -218,6 +218,8 @@
   Patch162:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.162
   Patch163:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.163
   Patch164:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.164
  +Patch165:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.165
  +Patch166:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.166
   
   #   build information
   Prefix:       %{l_prefix}
  @@ .
______________________________________________________________________
OpenPKG                                             http://openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to