[Buildroot] [git commit] docs/header.html: Add link to patchwork

[Buildroot] [git commit] docs/header.html: Add link to patchwork

[Peter Korsgaard]

commit: http://git.buildroot.net/buildroot/commit/?id=3d629c405f601bdb9aa7f939f274a52a012e6561
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 docs/header.html |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/docs/header.html b/docs/header.html
index a20f235..ce5d555 100644
--- a/docs/header.html
+++ b/docs/header.html
@@ -55,6 +55,7 @@
     <br><a href="/docs.html">Documentation</a>
     <br><a href="/lists.html">Mailing Lists</a>
     <br><a href="http://autobuild.buildroot.org">Autobuilder</a>
+    <br><a href="http://patchwork.buildroot.org">Patchwork</a>
 
     <p><b>Related Sites</b>
     <br><a href="http://busybox.net/">BusyBox</a>

[Buildroot] [git commit] docs/header.html: Add link to patchwork

[Thomas De Schampheleire]

Hi,

On Sat, Apr 21, 2012 at 1:18 PM, Peter Korsgaard <jacmet@sunsite.dk> wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=3d629c405f601bdb9aa7f939f274a52a012e6561
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> ---
> ?docs/header.html | ? ?1 +
> ?1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/docs/header.html b/docs/header.html
> index a20f235..ce5d555 100644
> --- a/docs/header.html
> +++ b/docs/header.html
> @@ -55,6 +55,7 @@
> ? ? <br><a href="/docs.html">Documentation</a>
> ? ? <br><a href="/lists.html">Mailing Lists</a>
> ? ? <br><a href="http://autobuild.buildroot.org">Autobuilder</a>
> + ? ?<br><a href="http://patchwork.buildroot.org">Patchwork</a>

I did not see any other mention about this, and haven't been active on
IRC for a while, so I was happily surprised to see this link (actually
it was Yegor's resend of some patches that triggered me, I hadn't seen
this mail yet).

What is the plan exactly?
Everyone can change the state of their own patches, e.g. to indicate
that they intend to send a new version based on feedback. But what
about delegating? When is it done? Will Peter delegate those patches
that he intends to accept to himself, or should developers that
consider their patches as 'final' delegate to Peter ?

Thanks,
Thomas

[Buildroot] [git commit] docs/header.html: Add link to patchwork

[Peter Korsgaard]

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:

Hi,

 Thomas> I did not see any other mention about this, and haven't been
 Thomas> active on IRC for a while, so I was happily surprised to see
 Thomas> this link (actually it was Yegor's resend of some patches that
 Thomas> triggered me, I hadn't seen this mail yet).

 Thomas> What is the plan exactly?

Basically like we discussed at the dev day:

http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html

E.G. I've set it up together with the ozlabs / osuosl guys, so we can
now start playing with it to se what works / what doesn't work for us.

 Thomas> Everyone can change the state of their own patches, e.g. to indicate
 Thomas> that they intend to send a new version based on feedback. But what
 Thomas> about delegating? When is it done? Will Peter delegate those patches
 Thomas> that he intends to accept to himself, or should developers that
 Thomas> consider their patches as 'final' delegate to Peter ?

I'm still very much a patchwork noob, so I don't quite know yet what's
possible / what work flow makes most sense.

To begin with I'll setup two things:

- Ensure patchwork doesn't think git commit mails are new patches (done)
- Ensure patchwork state gets updated whenever I push commits (still to
  be done)

-- 
Bye, Peter Korsgaard