From: Lea Wiemann <lewiemann@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: fix support for repository directories with spaces
Date: Wed, 18 Jun 2008 00:07:00 +0200 [thread overview]
Message-ID: <48583584.6030906@gmail.com> (raw)
In-Reply-To: <m3k5goon7v.fsf@localhost.localdomain>
Jakub Narebski wrote:
> I'd like to do away with need for git_cmd_str(), but unfortunately it
> is needed in a place where git has to form pipeline, namely in
> creating externally compressed snapshot (in git_snapshot), and to
> redirect stderr to /dev/null in git_object.
git_objects's use of 2> /dev/null won't be necessary since the Git::Repo
API uses cat-file --batch-check, which doesn't (well, shouldn't) write
on stderr.
If the use of shell command lines in git_snapshot bothers us enough, we
can (a) create the pipe ourselves and just have it not work on Windows,
(b) create it ourselves and spend a lot of time working around Windows'
horribly borked API, or (c) use Perl's Zlib/Bzip2/LZO libraries. If
anything I'm in favor of (c), though it makes installation harder if you
want compressed tarballs. I'm fine with leaving it as is.
-- Lea
next prev parent reply other threads:[~2008-06-17 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 1:09 [PATCH] gitweb: fix support for repository directories with spaces Lea Wiemann
2008-06-17 1:14 ` Junio C Hamano
2008-06-17 21:27 ` Junio C Hamano
2008-06-17 21:46 ` [PATCH v2] gitweb: quote commands properly when calling the shell Lea Wiemann
2008-06-17 21:51 ` Lea Wiemann
2008-06-17 23:41 ` Junio C Hamano
2008-06-17 1:38 ` [PATCH] gitweb: fix support for repository directories with spaces Jakub Narebski
2008-06-17 22:07 ` Lea Wiemann [this message]
2008-06-17 22:27 ` Jakub Narebski
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=48583584.6030906@gmail.com \
--to=lewiemann@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).