Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn write access
Date: Thu, 6 Dec 2007 20:00:31 -0700	[thread overview]
Message-ID: <20071207030031.GA1309@codepoet.org> (raw)
In-Reply-To: <d6cda7730712042236r2dc72cdes911eb753935f2abe@mail.gmail.com>

On Wed Dec 05, 2007 at 04:36:59AM -0200, Thiago A. Corr?a wrote:
> Hi,
> 
>     Sorry if this is a bit out of line, but is there a policy on how
> to get svn write access? Should I just kindly ask for it? Should I
> just keep sending patches and wait for an invitation if they are ok? I
> see myself working quite a lot with buildroot lately and there is
> always some things that need fixing or tweaking to get things working,
> so being able to commit those changes would be really great.

http://buildroot.uclibc.org/developer.html

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

      reply	other threads:[~2007-12-07  3:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05  6:36 [Buildroot] svn write access Thiago A. Corrêa
2007-12-07  3:00 ` Erik Andersen [this message]

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=20071207030031.GA1309@codepoet.org \
    --to=andersen@codepoet.org \
    --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