Package: git
Version: 1:1.7.1-1.1ubuntu0.1
Severity: minor
Tags: patch

git-var(1) did not say that hardcoded fallback 'vi' may have been changed
at build time. A user could be puzzled if 'nano' pops up even when none of the
mentioned environment vars or config.editor are set. Clarify this.

Ideally, the build system should be changed to reflect the chosen fallback
editor when creating the man pages. Not sure if that is even possible though.



-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 
'maverick-backports'), (500, 'maverick')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-32-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages git depends on:
ii  libc6            2.12.1-0ubuntu10.4      Embedded GNU C Library: Shared lib
ii  libcurl3-gnutls  7.21.0-1ubuntu1.3       Multi-protocol file transfer libra
ii  libdigest-sha1-p 2.13-1                  NIST SHA-1 message digest algorith
ii  liberror-perl    0.17-1                  Perl module for error/exception ha
ii  libexpat1        2.0.1-7ubuntu1          XML parsing C library - runtime li
ii  perl-modules     5.10.1-12ubuntu2.1      Core Perl modules
ii  zlib1g           1:1.2.3.4.dfsg-3ubuntu1 compression library - runtime

Versions of packages git recommends:
ii  less                    436-1            pager program similar to more
ii  openssh-client [ssh-cli 1:5.5p1-4ubuntu6 secure shell (SSH) client, for sec
ii  patch                   2.6-2ubuntu1     Apply a diff file to an original
ii  rsync                   3.0.7-2ubuntu1.1 fast remote file copy program (lik

Versions of packages git suggests:
ii  git-arch            1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  git-cvs             1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  git-daemon-run      1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  git-doc             1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  git-email           1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  git-gui             1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  git-svn             1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  gitk                1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi
ii  gitweb              1:1.7.1-1.1ubuntu0.1 fast, scalable, distributed revisi

-- no debconf information
>From 821e9719c021200f2a37b7f7c9e2f2c1117ae676 Mon Sep 17 00:00:00 2001
From: Rodrigo Silva (MestreLion) <li...@rodrigosilva.com>
Date: Thu, 29 Mar 2012 21:06:17 -0300
Subject: [PATCH] Documentation: replace 'vi' for 'editor' to reflect build-time 
option

git-var(1) did not say that hardcoded fallback 'vi' may have been changed
at build time. A user could be puzzled if 'nano' pops up even when none of the
mentioned environment vars or config.editor are set. Clarify this.

Ideally, the build system should be changed to reflect the chosen fallback
editor when creating the man pages. Not sure if that is even possible though.

Signed-off-by: Rodrigo Silva (MestreLion) <li...@rodrigosilva.com>
---
 Documentation/git-var.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-var.txt b/Documentation/git-var.txt
index 5317cc2..e388c6e 100644
--- a/Documentation/git-var.txt
+++ b/Documentation/git-var.txt
@@ -43,7 +43,7 @@ GIT_EDITOR::
     `$SOME_ENVIRONMENT_VARIABLE`, `"C:\Program Files\Vim\gvim.exe"
     --nofork`.  The order of preference is the `$GIT_EDITOR`
     environment variable, then `core.editor` configuration, then
-    `$VISUAL`, then `$EDITOR`, and then finally 'vi'.
+    `$VISUAL`, then `$EDITOR`, and then finally 'editor'.
 
 GIT_PAGER::
     Text viewer for use by git commands (e.g., 'less').  The value
-- 
1.7.1

Reply via email to