From: Junio C Hamano <gitster@pobox.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] git checkout $tree path
Date: Tue, 04 Oct 2011 19:07:04 -0700 [thread overview]
Message-ID: <7v1uusb393.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAG+J_Dy7gnDEK-9KAJT4M_wumS_QpzLNMVzAiOHCyEbFBU65=w@mail.gmail.com> (Jay Soffian's message of "Tue, 4 Oct 2011 11:05:11 -0400")
Jay Soffian <jaysoffian@gmail.com> writes:
> I think I'd expect the first behavior with:
>
> $ git checkout master -- dir/*
If we did not have to worry about "dir/.gitignore", this proposal does
have certain attractiveness.
prev parent reply other threads:[~2011-10-05 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 22:46 [RFC/PATCH] git checkout $tree path Junio C Hamano
2011-09-30 1:02 ` John Szakmeister
2011-10-03 10:26 ` Jeff King
2011-10-03 16:08 ` Junio C Hamano
2011-10-04 7:42 ` Jeff King
2011-10-04 15:20 ` Junio C Hamano
2011-10-04 15:05 ` Jay Soffian
2011-10-05 2:07 ` Junio C Hamano [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=7v1uusb393.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=peff@peff.net \
/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).