Below you can see which patches edev and e2coders have been up to. The patchee column is the piece of code that has been patched, patcher is the person doing the patch. Hopefully the next column has an explanation of what the path is supposed to do, and the last column says which coder-admin (usually a member of e2coders or %%) is ultimately responsible for the patch.

See also Patch Importer.

The status of each patch can be

pending review

The patch has been submitted but no coder admin has yet looked it over.

invalid

The patch has a mistake and will not be applied, or was temporarily applied for whatever reason but is not going to be reapplied again.

assigned

A coder admin has claimed dibs on the patch or someone else has decided that the assigned person is responsible for it.

later

The patch looks like a good idea but cannot be applied right now for whatever reason (e.g. another patch elsewhere has to be applied jointly with this one and the other patch hasn't been written yet).

undone

The patch has been temporarily undone because a coder is currently working on it. Its status should eventually be moved to one of the other statuses.

implemented

The patch is now running code and a part of the database.

Notice that these are only the patches for code that is housed in the database itself. For patches to the running ecore, we have a Mercurial repository that you can also check up on. Lastly, if you are a member of edev and don't know what this is all about, I recommend reading edev: Quickstart or the Coding for E2 series.

Select your filters:

Now: 1 – 100
next 101 – 200