git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Raible <raible@nextest.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: sparse checkout using exclusions
Date: Mon, 31 Oct 2011 13:16:13 -0700	[thread overview]
Message-ID: <4EAF020D.9090305@nextest.com> (raw)
In-Reply-To: <CALkWK0=X4O9jBbx_ZDXbtnDCmTb9fHbm13Z-pqTNBooA0Z=c0g@mail.gmail.com>

On 10/28/2011 10:46 PM, Ramkumar Ramachandra wrote:
> 
> This issue was fixed in 5e821231 (git-read-tree.txt: update sparse
> checkout examples, 2011-09-26).
> 
> Cheers.
> 
> -- Ram

git tag -l --contains => v1.7.8-rc0

I'm running 1.7.7.1.msysgit.0, so I don't have it yet.
And neither do any of the online man pages I could find.

But I'm happy that it's fixed.  And the commit message is
better than what I would have come up with.

Thanks - Eric

      reply	other threads:[~2011-10-31 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29  0:17 sparse checkout using exclusions Eric Raible
2011-10-29  5:46 ` Ramkumar Ramachandra
2011-10-31 20:16   ` Eric Raible [this message]

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=4EAF020D.9090305@nextest.com \
    --to=raible@nextest.com \
    --cc=artagnon@gmail.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).