public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Puneet Maheshwari" <puneetrocks@gmail.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Register a new package
Date: Mon, 02 Jul 2007 23:16:00 -0000	[thread overview]
Message-ID: <588212940707021616g7e6c2e99kcb4198cba82779fe@mail.gmail.com> (raw)
In-Reply-To: <46898223.4020907@mlbassoc.com>

When I add a new package, do I manually need to edit ecos.db file and
write the entry for this new package.

Than

On 7/2/07, Gary Thomas <gary@mlbassoc.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Puneet Maheshwari wrote:
> > Hi,
> >
> > When we have to register a new package in ecos.db, how do we
> > accomplish that? i.e. when we add a new package and we want to
> > register that.
>
> What do you mean "register"?  If you add packages to ecos.db,
> then you can make [local] use of those packages.  If you want
> them included in the public CVS, you'll have to submit them
> for approval.  We would also need a copyright assignment for
> the files.  See http://ecos.sourceware.org/assign.html
>
> - --
> - ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> - ------------------------------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFGiYIimaKbSsQGV8ARAomJAJsGzlERZ43CNMGVopB2OpG8P7zgwQCgnmnx
> 6W/9WqSKFplciD93MqX9Smw=
> =9G1Y
> -----END PGP SIGNATURE-----
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-07-02 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 22:11 Puneet Maheshwari
2007-07-02 22:54 ` Gary Thomas
2007-07-02 23:16   ` Puneet Maheshwari [this message]
2007-07-03  1:10     ` Gary Thomas

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=588212940707021616g7e6c2e99kcb4198cba82779fe@mail.gmail.com \
    --to=puneetrocks@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    /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).