From: Sergio Callegari <scallegari@arces.unibo.it>
To: git@vger.kernel.org
Subject: gitk does not appreciate file names including spaces
Date: Thu, 12 Oct 2006 16:45:36 +0200 [thread overview]
Message-ID: <452E5510.9090002@arces.unibo.it> (raw)
Just a short notice about it. Not a big issue, really... just that in the
quadrant at the bottom right of the gitk screen, filenames including spaces
are not shown properly.
Sergio
--
----------------------------------------------------------------
Dr. Sergio Callegari Via Fontanelle 40
Researcher 47100 Forlì
II School of Engineering Tel. +39.0543.786927
University of Bologna Fax. +39.0543.786926
Affiliated with:
DEIS - Dept. of Electronics, Computer Sciences and Systems,
University of Bologna (www.deis.unibo.it)
ARCES - Advanced Research Center on Electronic Systems for
Information and Communication Technologies
Unversity of Bologna (www.arces.unibo.it)
================================================================
next reply other threads:[~2006-10-12 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 14:45 Sergio Callegari [this message]
[not found] ` <11606654193083-git-send-email-rayl@mail.com>
2006-10-12 15:03 ` [PATCH] [PATCH] gitk: Handle spaces in filenames Ray Lehtiniemi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=452E5510.9090002@arces.unibo.it \
--to=scallegari@arces.unibo.it \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).