From: "Lars R. Damerow" <lars@pixar.com>
To: git@vger.kernel.org
Subject: [PATCH 0/2] Add support for GIT_ONE_FILESYSTEM (resubmission)
Date: Tue, 16 Mar 2010 15:04:59 -0700 [thread overview]
Message-ID: <1268777101-22122-1-git-send-email-lars@pixar.com> (raw)
Hi all,
I incorporated the feedback I got into a new patch for
GIT_ONE_FILESYSTEM. It uses git_env_bool, doesn't do getenv calls within
the loop, and reports better error messages.
git_env_bool was marked static in config.c, so I had to remove that to
make it available in setup.c.
Lars R. Damerow (2):
config.c: remove static keyword from git_env_bool()
Add support for GIT_ONE_FILESYSTEM
Documentation/git.txt | 3 +++
cache.h | 1 +
config.c | 2 +-
setup.c | 17 ++++++++++++++++-
4 files changed, 21 insertions(+), 2 deletions(-)
next reply other threads:[~2010-03-16 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 22:04 Lars R. Damerow [this message]
2010-03-16 22:05 ` [PATCH 1/2] config.c: remove static keyword from git_env_bool() Lars R. Damerow
2010-03-16 22:05 ` [PATCH 2/2] Add support for GIT_ONE_FILESYSTEM Lars R. Damerow
2010-03-17 0:45 ` Nguyen Thai Ngoc Duy
2010-03-17 7:09 ` Johannes Sixt
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=1268777101-22122-1-git-send-email-lars@pixar.com \
--to=lars@pixar.com \
--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).