From: "Michael K. Edwards" <medwards.linux@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make "git checkout <branch> <path>" work when <path> is a directory.
Date: Thu, 16 Nov 2006 22:18:57 -0800 [thread overview]
Message-ID: <f2b55d220611162218t3a752829hf922613c17fe326d@mail.gmail.com> (raw)
In-Reply-To: <7vlkmavcai.fsf@assigned-by-dhcp.cox.net>
Ah. Missed that patch, which is indeed a superset of mine. Looks
like you committed it on branch "next"; is that a personal
experimental branch, or the integration branch against which patches
should be generated?
Cheers,
next prev parent reply other threads:[~2006-11-17 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 5:49 [PATCH] Make "git checkout <branch> <path>" work when <path> is a directory Michael K. Edwards
2006-11-17 6:04 ` Junio C Hamano
2006-11-17 6:18 ` Michael K. Edwards [this message]
2006-11-17 8:15 ` Junio C Hamano
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=f2b55d220611162218t3a752829hf922613c17fe326d@mail.gmail.com \
--to=medwards.linux@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).