Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] HEADS UP: svn->git transition
Date: Thu, 30 Apr 2009 21:05:18 +0200	[thread overview]
Message-ID: <87fxfq9d3l.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200904302047.33996.vda.linux@googlemail.com> (Denys Vlasenko's message of "Thu\, 30 Apr 2009 20\:47\:33 +0200")

>>>>> "Denys" == Denys Vlasenko <vda.linux@googlemail.com> writes:

Hi,

 Denys> Which email are you referring to?

Ehm, the mails between us and osuosl.org staff about switching the
uclibc.org projects from svn to git. The first mail was afaik:

From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Subject: uClibc: switching from svn to git
To: support at osuosl.org
Cc: vapier at gentoo.org, solar at gentoo.org, vda.linux at googlemail.com,
	jacmet at uclibc.org
Date: Wed, 18 Feb 2009 21:16:54 +0100

Did you never read them?

 >> So why didn't you do anything about it in the last month?

 Denys> I didn't do anything because I am not a person which performs
 Denys> svn->git migration. I am just one of svn users (which happens
 Denys> to have write access too).

.. And busybox maintainer.

 Denys> So far I read all relevant emails and I do not see instructions
 Denys> how can I check out new tree. (I will also need instructions
 Denys> how to push/commit/latest_fashionable_term_of_the_week_for_it
 Denys> changes).

Again, my mail to the buildroot list described the setup for BR. I
don't quite know how you will do it for busybox / uclibc, but the
basic stuff stays the same.

To quote:

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

replace buildroot with busybox or uclibc and you should be good to go.

 Denys> Such instructions can't possibly be longer than 2 to 5 lines.
 Denys> This is the minimum necessary for users and developers to migrate.
 Denys> If I missed an email which contains them, I apoligize.

More like 73 mails ;)

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2009-04-30 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 11:38 [Buildroot] HEADS UP: svn->git transition Bernhard Reutner-Fischer
     [not found] ` <49F85AF3.4060501@t-online.de>
2009-04-29 12:55   ` Gaye Abdoulaye Walsimou
     [not found]     ` <20090429132312.GA2431@yoda.jdub.homelinux.org>
2009-04-29 13:40       ` Gaye Abdoulaye Walsimou
2009-04-29 13:43       ` Peter Korsgaard
2009-04-29 14:34   ` Bernhard Reutner-Fischer
2009-04-29 14:46     ` Asbjoern Laurberg
     [not found]     ` <200904300153.39528.vda.linux@googlemail.com>
2009-04-30  6:12       ` Peter Korsgaard
     [not found]         ` <200904301248.33425.vda.linux@googlemail.com>
2009-04-30 11:32           ` Peter Korsgaard
     [not found]             ` <200904302047.33996.vda.linux@googlemail.com>
2009-04-30 19:05               ` Peter Korsgaard [this message]
     [not found]     ` <49FB2082.2000501@gmail.com>
     [not found]       ` <200905011856.30347.vda.linux@googlemail.com>
2009-05-01 17:05         ` Gaye Abdoulaye Walsimou
2009-04-29 15:49 ` Bernhard Reutner-Fischer

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=87fxfq9d3l.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