From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: npm thoughts
Date: Tue, 28 Feb 2017 11:56:35 -0500 [thread overview]
Message-ID: <20170228165635.GA16277@linux-uys3> (raw)
In-Reply-To: <20170228045004.GA5913@linux-uys3>
My first thought is that "devtool add ..." shouldn't act differently depending
on whether it is pointed at a checkout of the code or whether it is pointed at
the code's npm repository.
next prev parent reply other threads:[~2017-02-28 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 4:50 npm thoughts Trevor Woerner
2017-02-28 16:56 ` Trevor Woerner [this message]
2017-02-28 18:00 ` Trevor Woerner
2017-03-03 10:26 ` Josef Holzmayr
2017-03-06 7:24 ` Anders Darander
2017-02-28 18:19 ` Trevor Woerner
2017-03-03 10:45 ` Josef Holzmayr
2017-03-03 10:57 ` Alexander Kanavin
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=20170228165635.GA16277@linux-uys3 \
--to=twoerner@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox