oe-linux-nfc.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mark Greer <mgreer@animalcreek.com>
To: linux-nfc@lists.01.org
Subject: Re: [PATCH v2] ndef: Only register interface for known records
Date: Sun, 10 Nov 2019 21:37:33 -0700	[thread overview]
Message-ID: <20191111043733.GB2789@animalcreek.com> (raw)
In-Reply-To: <CAPybu_2+p6vzPnmD05jBksRdAH8sYwPYeojU_FrmCOmY_dN=kg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

> On Sat, Nov 9, 2019 at 9:38 PM Mark Greer <mgreer@animalcreek.com> wrote:
> > On Fri, Nov 08, 2019 at 10:05:01AM +0100, Samuel Ortiz wrote:
> > > What about moving the neard repo to github and have you or Ricardo (or
> > > both) maintain it from there?
> >
> > I'm okay with that but I am really busy these days.  I'll do what I
> > can but I know I won't be very prompt.  Ricardo, can you help me with
> > that?

On Sun, Nov 10, 2019 at 05:37:29PM +0100, Ricardo Ribalda Delgado wrote:
> Unfortunately I cannot contribute much. I am not using neard everyday,
> it is not my area of expertise and I just got a baby #2, so not much
> time left for hacking :).

Darn :(   (but congrats on the new baby)

I'm not working with it everyday either but as long as people are patient,
I'll do what I can.

I'll shake off the neard cobwebs and send an email with more info in the
next few weeks.

Mark
--

  reply	other threads:[~2019-11-11  4:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191109203830.GA31348@animalcreek.com>
2019-11-10 16:37 ` [PATCH v2] ndef: Only register interface for known records Ricardo Ribalda Delgado
2019-11-11  4:37   ` Mark Greer [this message]
     [not found] <20191108040813.GA19844@animalcreek.com>
2019-11-08  9:05 ` Samuel Ortiz
     [not found] <20180930233513.GA16410@animalcreek.com>
2019-11-06 14:13 ` Ricardo Ribalda Delgado

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=20191111043733.GB2789@animalcreek.com \
    --to=mgreer@animalcreek.com \
    --cc=linux-nfc@lists.01.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 read-only IMAP folder(s) and NNTP newsgroup(s).