Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Urban <urban@unix-beratung.de>
To: buildroot@busybox.net
Subject: [Buildroot] contributions to buildroot...
Date: Sun, 26 Apr 2009 16:14:09 +0200	[thread overview]
Message-ID: <49F46C31.6050005@unix-beratung.de> (raw)

Hi Folks,

a while ago (15th of March) I submitted a new package, "ndyndns-1.14" via
the mailing list.  It doesn't seem to have made it into the repository.

I don't personally care whether it ever makes it into the repo. I've can
always add it to the stuff I check out.  I do however wonder why it didn't
make it in.  I understand that you guys probably have more on your lists
than you can ever hope to accomplish.  I appreciate your effort very much.
I would be helpful to me to know whether my submission was rejected, and
why, or whether it's simply fallen by the wayside, which, as I said, is also
ok.  I submitted it because somewhere you guys have an exhortation to make
packages available to others...

thanks,

Rob Urban

             reply	other threads:[~2009-04-26 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 14:14 Robert Urban [this message]
2009-04-26 20:05 ` [Buildroot] contributions to buildroot Peter Korsgaard

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=49F46C31.6050005@unix-beratung.de \
    --to=urban@unix-beratung.de \
    --cc=buildroot@busybox.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