From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] fetch2/git: fix subpath destination directory
Date: Sat, 17 Sep 2011 11:54:16 +0100 [thread overview]
Message-ID: <201109171154.16365.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <d77660aa9085af99cdb0aa4d38736b8485434697.1316178644.git.paul.eggleton@linux.intel.com>
Hmm, this patch is broken for subpath depth > 1. Please disregard; will send a
v2 soon.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-09-17 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 13:21 [PATCH 0/1] Fix git fetcher subpath option Paul Eggleton
2011-09-16 13:21 ` [PATCH 1/1] fetch2/git: fix subpath destination directory Paul Eggleton
2011-09-17 10:54 ` Paul Eggleton [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-17 11:03 [PATCH 0/1] Fix git fetcher subpath option v2 Paul Eggleton
2011-09-17 11:03 ` [PATCH 1/1] fetch2/git: fix subpath destination directory Paul Eggleton
2011-09-19 11:34 ` Richard Purdie
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=201109171154.16365.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.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.