From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] misc development news
Date: Tue, 31 Mar 2009 23:23:03 +0200 [thread overview]
Message-ID: <874ox99yko.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <87d4d4md5o.fsf@macbook.be.48ers.dk> (Peter Korsgaard's message of "Fri\, 27 Feb 2009 10\:39\:47 +0100")
>>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:
Hi,
Peter> - svn->git: Migration is starting to take shape. We have digged
Peter> through svn history and found proper author/email info for all
Peter> developers for the conversion, and the osuosl.org staff is setting
Peter> up gitweb, commit notifications and various minor stuff for the
Peter> conversion. Expect more info in ~1 weeks time.
Ok - Timing was "slightly" off, but the svn->git migration
uclibc.org-wide is almost completed. The repo can be browsed through
cgit at:
http://git.buildroot.net/buildroot/
It can be cloned anonymously using:
git clone git://git.buildroot.net/buildroot/ or
git clone http://git.buildroot.net/buildroot/ if you're behind a
firwall blocking git access.
Developers can also access the repo over ssh with:
git clone ssh://uclibc.org/var/lib/git/buildroot.git
But notice that you don't have write access, so you cannot push
changes directly. Instead push your changes to your own tree and send
pull requests to the list. You can add personal repos on uclibc.org by
storing them in ~/git/ and touching ~/git/<repo>/git-daemon-export-ok,
after which the hourly cronjob will pick them up and show them in
cgit.
I would like us to move to a setup similar to the kernel/uboot, where
all changes get posted to the list before they get committed to the
tree, and with package / sub-tree maintainers.
The repo was synched on the 17th, so it's missing the latest
changes. The svn repo will be turned read only once the final sync is
done, but more info about that later.
Peter> - release: We're still on track for a 2009.05 release. Remember, the
Peter> tree closes end April for new features when I'll cut the first
Peter> release candidate. See
Peter> http://lists.busybox.net/pipermail/buildroot/2009-February/025974.html
Peter> for more details.
This is still the case. The aim is currently to close the tree for new
features and release 2009.05-rc1 sometime in the weekend 24-25th of
April.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-03-31 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 9:39 [Buildroot] misc development news Peter Korsgaard
2009-02-27 22:05 ` Markus Heidelberg
2009-02-27 23:09 ` Peter Korsgaard
2009-03-31 21:23 ` Peter Korsgaard [this message]
2009-04-01 4:47 ` Thiago A. Corrêa
2009-04-28 21:22 ` Peter Korsgaard
2009-04-29 14:58 ` Thiago A. Corrêa
2009-04-29 21:00 ` Markus Heidelberg
2009-04-29 21:17 ` Thiago A. Corrêa
2009-05-01 18:57 ` Markus Heidelberg
2009-04-30 14:03 ` Peter Korsgaard
2009-05-01 19:03 ` Markus Heidelberg
2009-04-30 13:50 ` Peter Korsgaard
2009-04-06 0:22 ` Thomas Petazzoni
2009-04-06 7:45 ` Peter Korsgaard
2009-04-29 9:44 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 17:13 Darcy Watkins
[not found] <mailman.6835.1239009687.25474.buildroot@busybox.net>
2009-04-06 19:01 ` Frank Hoeflich
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=874ox99yko.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.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