Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Ketan Kulkarni <ketkulka@gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Cc: cerowrt developers <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] administrative questions
Date: Wed, 30 Jan 2013 09:54:09 +0530	[thread overview]
Message-ID: <CAD6NSj7OpQRxfz68Z4qFHyS74XgT0GK7p0V-25JppJSt+se7+g@mail.gmail.com> (raw)
In-Reply-To: <5108180E.4030602@gmail.com>

Hi William,
To add issues and do tracking, you need to register. Once registered,
I can provide you the required access.
If you have registered already, please let me know your login id so I
can grant access. I couldn't find you in the user's list.

Downloading the archives is a problem for everyone which I think
Dave(?) needs to address.

You can submit the patches to this list, ccing Dave, or you can attach
it to the reported bugs for better future tracking.
All standard linux formatting applies here as well.

Thanks,
Ketan

On Wed, Jan 30, 2013 at 12:12 AM, William Allen Simpson
<william.allen.simpson@gmail.com> wrote:
> This link (and all the other Archives links):
>
>   https://lists.bufferbloat.net/pipermail/cerowrt-devel/2013-January.txt.gz
>
> gives an error message:
>
> Forbidden
>
> You don't have permission to access /pipermail/ on this server.
> Apache/2.2.16 (Ubuntu) Server at lists.bufferbloat.net Port 443
>
> This happens whether I am either logged in or not logged in to my account.
>
> ===
>
> How do we get permission to add "Issues" and do tracking?
>
> ===
>
> How do we submit patches?  Preferred format?
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

  reply	other threads:[~2013-01-30  4:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 18:42 William Allen Simpson
2013-01-30  4:24 ` Ketan Kulkarni [this message]
2013-01-30 16:49   ` William Allen Simpson
2013-01-31  3:03     ` Ketan Kulkarni
2013-01-31 16:28       ` William Allen Simpson
2013-01-31 17:43       ` William Allen Simpson
2013-02-01 15:51         ` Ketan Kulkarni
2013-02-04  6:06           ` Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAD6NSj7OpQRxfz68Z4qFHyS74XgT0GK7p0V-25JppJSt+se7+g@mail.gmail.com \
    --to=ketkulka@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=william.allen.simpson@gmail.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