Your message dated Tue, 17 Feb 2009 09:41:08 +0000
with message-id 
<20090217094108.12382.qm...@73d4f407af9f13.315fe32.mid.smarden.org>
and subject line Re: Bug#493934: /etc/bash_completion.d/git: Completing ref 
name with trailing '.' gives '..' rather than refs
has caused the Debian Bug report #493934,
regarding /etc/bash_completion.d/git: Completing ref name with trailing '.' 
gives '..' rather than refs
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 [email protected]
immediately.)


-- 
493934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493934
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-core
Version: 1:1.5.6.2-1
Severity: normal
File: /etc/bash_completion.d/git

With bash completion turned on, completing a partial branch name with
a trailing '.' assumes that the '.' represents the start of ".." to
separate two refs in a range.  Thus, if I tab-complete "v2.6." in a
kernel tree, I get "v2.6.." rather than a much more useful list of
tags or branches starting with "v2.6.".

- Josh Triplett

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-core depends on:
ii  libc6                  2.7-13            GNU C Library: Shared libraries
ii  libcurl3-gnutls        7.18.2-7          Multi-protocol file transfer libra
ii  libdigest-sha1-perl    2.11-2+b1         NIST SHA-1 message digest algorith
ii  liberror-perl          0.17-1            Perl module for error/exception ha
ii  libexpat1              2.0.1-4           XML parsing C library - runtime li
ii  perl-modules           5.10.0-11.1       Core Perl modules
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages git-core recommends:
ii  less                          418-1      Pager program similar to more
ii  openssh-client [ssh-client]   1:5.1p1-2  secure shell client, an rlogin/rsh
ii  patch                         2.5.9-5    Apply a diff file to an original
ii  rsync                         3.0.3-2    fast remote file copy program (lik

Versions of packages git-core suggests:
pn  git-arch                     <none>      (no description available)
pn  git-cvs                      <none>      (no description available)
pn  git-daemon-run               <none>      (no description available)
pn  git-doc                      <none>      (no description available)
pn  git-email                    <none>      (no description available)
pn  git-gui                      <none>      (no description available)
ii  git-svn                      1:1.5.6.2-1 fast, scalable, distributed revisi
ii  gitk                         1:1.5.6.2-1 fast, scalable, distributed revisi
pn  gitweb                       <none>      (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1:1.5.6.5-1

On Sat, Aug 09, 2008 at 05:25:02PM -0500, Jonathan Nieder wrote:
> tags + fixed-upstream
> Josh Triplett wrote:
> > With bash completion turned on, completing a partial branch name with
> > a trailing '.' assumes that the '.' represents the start of ".." to
> > separate two refs in a range.  Thus, if I tab-complete "v2.6." in a
> > kernel tree, I get "v2.6.." rather than a much more useful list of
> > tags or branches starting with "v2.6.".
> 
> This is addressed in commit 6c36c9e 'bash completion: Don't offer "a.."
> as a completion for "a."', part of upstream release 1.5.6.4.

Thanks!


--- End Message ---

Reply via email to