[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#736939: marked as done (ITP: vim-fugitive -- Vim plugin to work with Git)

Your message dated Mon, 10 Feb 2014 16:00:09 +0000
with message-id <E1WCtHF-0006tn-ST@franck.debian.org>
and subject line Bug#736939: fixed in vim-fugitive 2.0-1
has caused the Debian Bug report #736939,
regarding ITP: vim-fugitive -- Vim plugin to work with Git
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
736939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736939
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Andrea Capriotti <capriott@debian.org>

* Package name    : vim-fugitive
  Version         : 2.0
  Upstream Author : Tim Pope <vim.org@tpope.org>
* URL             : http://www.vim.org/scripts/script.php?script_id=2975
* License         : Vim license
  Programming Lang: Vim
  Description     : A Git wrapper so awesome, it should be illegal

 I'm not going to lie to you; fugitive.vim may very well be the best Git
 wrapper of all time. Check out these features:

 View any blob, tree, commit, or tag in the repository with :Gedit
 (and :Gsplit, :Gvsplit, :Gtabedit, ...). Edit a file in the index and write to
 it to stage the changes. Use :Gdiff to bring up the staged version of the file
 side by side with the working tree version and use Vim's diff handling
 capabilities to stage a subset of the file's changes.

 Bring up the output of git status with :Gstatus. Press - to add/reset a file's
 changes, or p to add/reset --patch that mofo. And guess what :Gcommit does!

 :Gblame brings up an interactive vertical split with git blame output. Press
 enter on a line to edit the commit where the line changed, or o to open it in
 a split. When you're done, use :Gedit in the historic buffer to go back to the
 work tree version.

 :Gmove does a git mv on a file and simultaneously renames the buffer. :Gremove
 does a git rm on a file and simultaneously deletes the buffer.

 Use :Ggrep to search the work tree (or any arbitrary commit) with git grep,
 skipping over that which is not tracked in the repository. :Glog loads all
 previous revisions of a file into the quickfix list so you can iterate over
 them and watch the file evolve!

 :Gread is a variant of git checkout -- filename that operates on the buffer
 rather than the filename. This means you can use u to undo it and you never
 get any warnings about the file changing outside Vim. :Gwrite writes to both
 the work tree and index versions of a file, making it like git add when called
 from a work tree file and like git checkout when called from the index or a
 blob in history.

 Use :Gbrowse to open the current file on GitHub, with optional line range (try
 it in visual mode!). If your current repository isn't on GitHub, git instaweb
 will be spun up instead.

 Add %{fugitive#statusline()} to 'statusline' to get an indicator with the
 current branch in (surprise!) your statusline.

 Last but not least, there's :Git for running any arbitrary command, and Git!
 to open the output of a command in a temp file.

--- End Message ---
--- Begin Message --- 
Source: vim-fugitive
Source-Version: 2.0-1

We believe that the bug you reported is fixed in the latest version of
vim-fugitive, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 736939@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrea Capriotti <capriott@debian.org> (supplier of updated vim-fugitive package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 14:08:36 +0100
Source: vim-fugitive
Binary: vim-fugitive
Architecture: source all
Version: 2.0-1
Distribution: unstable
Urgency: low
Maintainer: Andrea Capriotti <capriott@debian.org>
Changed-By: Andrea Capriotti <capriott@debian.org>
Description: 
 vim-fugitive - Vim plugin to work with Git
Closes: 736939
Changes: 
 vim-fugitive (2.0-1) unstable; urgency=low
 .
   * Initial release (Closes: #736939)
Checksums-Sha1: 
 572ea13544b3fe6a91c50515705b6293fd7bc6da 1081 vim-fugitive_2.0-1.dsc
 460909760d7bfba546a4b039aec734e60d3cf367 26725 vim-fugitive_2.0.orig.tar.gz
 0365b9ee97db53b2c419013dbdf0def6fba4072c 3840 vim-fugitive_2.0-1.debian.tar.xz
 3fb47d2e5432d9a034ed776067b3cab221ecacd9 28504 vim-fugitive_2.0-1_all.deb
Checksums-Sha256: 
 f7d8cebb508f11732b073694d0fbd51c65704c7187b8dd48f91f255ca6cb6a29 1081 vim-fugitive_2.0-1.dsc
 3e5029499a157b0ba23d86280bd48e760cb2b5357a88d03115a483808e07a455 26725 vim-fugitive_2.0.orig.tar.gz
 e0bbed00ec6565b9e30b974dbc774138467daecaeee56cad7c021c047b962ab9 3840 vim-fugitive_2.0-1.debian.tar.xz
 4278dbc2b23b2f57f5231609f829c1a6e9b667dafaaebc24486ff00e040a425d 28504 vim-fugitive_2.0-1_all.deb
Files: 
 9ccec057c33e6960097803bd7b06dd78 1081 editors optional vim-fugitive_2.0-1.dsc
 2a393d2cd0a1146caa586fce96b14326 26725 editors optional vim-fugitive_2.0.orig.tar.gz
 4020a0313f7c594d7e81f9ab61454fe1 3840 editors optional vim-fugitive_2.0-1.debian.tar.xz
 4876a6667ea249ebd51f53c5f33e5df7 28504 editors optional vim-fugitive_2.0-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlLpRFoACgkQ4oPIaHg5igFtqwCeJoEw5qa3vDw5oHpoSlvl5cid
/ScAn0gffgnDtKzrB40WhDoU7tKH+4V9
=LBoT
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: