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

  Server: cvs.openpkg.org                  Name:   Christoph Schug
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-src                      Date:   07-Dec-2007 18:59:01
  Branch: HEAD                             Handle: 2007120717590000

  Modified files:
    openpkg-src/vim         vim.spec

  Log:
    upgrading package: vim 7.1.168 -> 7.1.170

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

  patch -p0 <<'@@ .'
  Index: openpkg-src/vim/vim.spec
  ============================================================================
  $ cvs diff -u -r1.572 -r1.573 vim.spec
  --- openpkg-src/vim/vim.spec  4 Dec 2007 07:46:40 -0000       1.572
  +++ openpkg-src/vim/vim.spec  7 Dec 2007 17:59:00 -0000       1.573
  @@ -25,7 +25,7 @@
   #   package versions
   %define       V_vl  7.1
   %define       V_vs  71
  -%define       V_pl  168
  +%define       V_pl  170
   
   #   package information
   Name:         vim
  @@ -38,7 +38,7 @@
   Group:        Editor
   License:      Charityware
   Version:      %{V_vl}.%{V_pl}
  -Release:      20071204
  +Release:      20071207
   
   #   package options
   %option       with_x11        no
  @@ -222,6 +222,8 @@
   Patch166:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.166
   Patch167:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.167
   Patch168:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.168
  +Patch169:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.169
  +Patch170:     ftp://ftp.vim.org/pub/vim/patches/%{V_vl}/%{V_vl}.170
   
   #   build information
   Prefix:       %{l_prefix}
  @@ .
______________________________________________________________________
OpenPKG                                             http://openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to