From: "Thiago A. Corrêa" <thiago.correa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Write access to SVN and bug tracker
Date: Fri, 31 Oct 2008 11:04:00 -0200 [thread overview]
Message-ID: <d6cda7730810310604o2f46cf03k2ee940fc0e0c340d@mail.gmail.com> (raw)
In-Reply-To: <C13DBBE85AD6974B85C118C35890CA5F13B21BEFA4@EU1RDCRDC1WX029.exi.nxp.com>
On Fri, Oct 31, 2008 at 7:24 AM, Daniel J Laird <daniel.j.laird@nxp.com> wrote:
> Good Idea, more the merrier.... (Expecially with the fact that you are using an external toolchain)
>
> I had to do the stuff mentioned on the website( create SSH key etc) - http://buildroot.uclibc.org/developer.html
>
> and then I had to send it to someone but not Erik Anderson. I sent it to vapier at uclibc.org.
>
> He created a username etc and then I can SVN over SSH and make my updates.
>
Mike <vapier@uclibc.org> doesn't track buildroot development, so he
will ask you to be vouched from current developers.
You have +1 from here.
next prev parent reply other threads:[~2008-10-31 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 9:14 [Buildroot] Write access to SVN and bug tracker Thomas Petazzoni
2008-10-31 9:24 ` Daniel J Laird
2008-10-31 13:04 ` Thiago A. Corrêa [this message]
2008-10-31 13:26 ` Thomas Petazzoni
2008-11-02 13:44 ` 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=d6cda7730810310604o2f46cf03k2ee940fc0e0c340d@mail.gmail.com \
--to=thiago.correa@gmail.com \
--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