From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] misc development news
Date: Fri, 1 May 2009 20:57:40 +0200 [thread overview]
Message-ID: <200905012057.40660.markus.heidelberg@web.de> (raw)
In-Reply-To: <d6cda7730904291417w3cc8d949u80e4eaf6db45b0d2@mail.gmail.com>
Thiago A. Corr?a, 29.04.2009:
> On Wed, Apr 29, 2009 at 6:00 PM, Markus Heidelberg
> > Peter seems to review many commits and fixes them or asks the committers
> > to fix them. So maybe the work isn't really less nowadays, but I'm not
> > sure.
> >
>
> Indeed unfortunally I don't offer as much help as I would like to, but
> at least I don't get in the way *smile*
> Imagine that on top of that, he would have to commit your patches, my
> patches, etc.
We can make his life easier with sending proper patch mails. Applying
them and committing will then be a rather automatic procedure.
> If we don't sort out how we are going to work, this move could just
> send ppl away, frustrated because we can't get things done.
The workflow and the problems before had sent people away, at least of
Bernhard I'm aware.
> I for one am still clueless on how should I continue to contribute,
> and yet I'm afraid that I will have to keep track of several different
> trees, on top of the 2 I already have (My private development +
> upstream buildroot).
Which extra trees do you think you need because of the changed workflow?
On the other hand, this is exactly which you can get much easier with
git in contrast to svn. Just create local branches as much as you need.
The data exchange between your private branch and the branch for your
changes that are meant for upstream also is pretty comfortable.
Markus
next prev parent reply other threads:[~2009-05-01 18:57 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
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 [this message]
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=200905012057.40660.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--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