From: Eric Raible <raible@nextest.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: sparse checkout using exclusions
Date: Fri, 28 Oct 2011 17:17:54 -0700 [thread overview]
Message-ID: <4EAB4632.5080101@nextest.com> (raw)
Hi all.
I was just about to send a long message about using exclusions
in sparse-checkout, when I did one last search and saw that all
of my problems were fixed by using '/*' instead of '*' as the
first line in .git/info/sparse-checkout.
Might it make sense for the example in git-read-tree.html to be
updated to include the leading slash?
/*
!unwanted
- Eric
next reply other threads:[~2011-10-29 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 0:17 Eric Raible [this message]
2011-10-29 5:46 ` sparse checkout using exclusions Ramkumar Ramachandra
2011-10-31 20:16 ` Eric Raible
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=4EAB4632.5080101@nextest.com \
--to=raible@nextest.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.