Discussion:
Adding an "easy" and "wip" patch stack
Robert Schwebel
2011-11-07 08:45:07 UTC
Permalink
Hi,

A next step we have agreed on is to add two example patch stacks, to
learn about the workflow:

1) an "easy" patch stack where we can quickly agree on
2) a more complicated one, which definitely needs some work.

Suggestions?

rsc

PS: The VM makes progress, but unfortunately we had some hardware issues
with new RAM on the host server. Our administration team is working
on this. However, it shouldn't slow down the progress, as we can use
my git tree posted some days ago in the meantime.
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Robert Schwebel
2011-11-28 09:51:59 UTC
Permalink
Post by Robert Schwebel
A next step we have agreed on is to add two example patch stacks, to
1) an "easy" patch stack where we can quickly agree on
2) a more complicated one, which definitely needs some work.
Suggestions?
Ping...

rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Esben Haabendal
2011-11-28 09:55:45 UTC
Permalink
Post by Robert Schwebel
Post by Robert Schwebel
A next step we have agreed on is to add two example patch stacks, to
1) an "easy" patch stack where we can quickly agree on
2) a more complicated one, which definitely needs some work.
Suggestions?
Ping...
Sounds fine to me, although personally I don't really care about such a
generalization, as I expect to handle each package and/or patch one at a
time.

/Esben

Loading...