Patchwork - Revision history

Sjhill: /* Which patches are tracked in patchwork? */

2012-09-06T18:06:01Z

‎Which patches are tracked in patchwork?

Sjhill at 13:25, 5 April 2012

2012-04-05T13:25:35Z

Ralf: Elaborate on when to resend patches and patch states.

2011-12-08T11:23:42Z

Elaborate on when to resend patches and patch states.

Ralf: /* See also */ Use protocol independent URL.

2011-12-02T17:40:26Z

‎See also: Use protocol independent URL.

Ralf: Extend article based on today's posting; add pointer to pwclient

2009-11-11T17:22:49Z

Extend article based on today's posting; add pointer to pwclient

Ralf: Created page with ''''Patchwork''' is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project. Patches that have been se…'

2009-10-15T14:29:42Z

Created page with ''''Patchwork''' is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project. Patches that have been se…'

New page

'''Patchwork''' is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.

Patches that have been sent to a mailing list are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too.

The project's maintainer can then scan through the list of patches, marking each with a certain state, such as Accepted, Rejected or Under Review. Old patches can be sent to the archive or deleted. A patch submitter can change the status of his patches for example when finding a bug or submitting a new version.

== See also ==
* http://patchwork.linux-mips.org The patchwork site for the Linux/MIPS project
* http://ozlabs.org/~jk/projects/patchwork The patch home page

@@ Line 24: / Line 24: @@
 == Which patches are tracked in patchwork? ==
-Patchwork has been installed on ''linux-mips.org'' in October [[2009]].  The [//www.linux-mips.org/archives/linux-mips linux-mips list archives] back to June 2009 were fed into patchworks, then manually walked through the hundreds of patches to ensure all patches have been handled.
+Patchwork was installed on ''linux-mips.org'' in October [[2009]]. The [//www.linux-mips.org/archives/linux-mips linux-mips list archives] back to June 2009 were fed into patchworks, then manually walked through the hundreds of patches to ensure all patches have been handled.
 == See also ==

← Older revision		Revision as of 13:25, 5 April 2012
Line 1:		Line 1:
−	'''Patchwork''' is a web-based patch tracking system designed to facilitate the contribution and management ~~of contributions to an open-source project. Patchwork is a web-based patch tracking system designed to faciliate the contribution and managment~~ of contributions to an open-source project. Patches that have been sent to a mailing list - the linux-mips list in this case - are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too.	+	'''Patchwork''' is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project. Patches that have been sent to a mailing list - the linux-mips list in this case - are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too.

	The project's maintainer can then scan through the list of patches, marking each with a certain state, such as Accepted, Rejected or Under Review. Old patches can be sent to the archive or deleted. A patch submitter can change the status of his patches for example when finding a bug or submitting a new version.		The project's maintainer can then scan through the list of patches, marking each with a certain state, such as Accepted, Rejected or Under Review. Old patches can be sent to the archive or deleted. A patch submitter can change the status of his patches for example when finding a bug or submitting a new version.

@@ Line 12: / Line 12: @@
 Beyond that it's largely up to the patch submitter.  For a submitter who doesn't use patchwork things will work the same way they used to work.
 == What new advanced features deos patchwork offer to submitters? ==
@@ Line 21: / Line 24: @@
 == Which patches are tracked in patchwork? ==
-I've installed patchworks about four weeks ago.  For testing purposes and also to ensure I've not dropped anything on the floor I've fed the mailing list archives back to June 2009 into patchworks, then manually walked through the hundreds of patches to ensure all patches have been handled.
+Patchwork has been installed on ''linux-mips.org'' in October [[2009]].  The [//www.linux-mips.org/archives/linux-mips linux-mips list archives] back to June 2009 were fed into patchworks, then manually walked through the hundreds of patches to ensure all patches have been handled.
-−
-If you've sent patches that have not been applied yet and don't show up in patchworks as new or under review, then please resent your patches.
 == See also ==

@@ Line 26: / Line 26: @@
 == See also ==
-* http://patchwork.linux-mips.org The patchwork site for the Linux/MIPS project
+* [//patchwork.linux-mips.org patchwork.linux-mips.org], the patchwork site for the Linux/MIPS project
 * http://ozlabs.org/~jk/projects/patchwork The patch home page
 * http://patchwork.kernel.org/help/pwclient [[pwclient]], a command line client for patchwork

@@ Line 1: / Line 1: @@
-'''Patchwork''' is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.
+'''Patchwork''' is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.  Patchwork is a web-based patch tracking system designed to faciliate the contribution and managment of contributions to an open-source project.  Patches that have been sent to a mailing list - the linux-mips list in this case - are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too.
-−
 Patches that have been sent to a mailing list are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too.
 The project's maintainer can then scan through the list of patches, marking each with a certain state, such as Accepted, Rejected or Under Review. Old patches can be sent to the archive or deleted.  A patch submitter can change the status of his patches for example when finding a bug or submitting a new version.
 == See also ==
 * http://patchwork.linux-mips.org The patchwork site for the Linux/MIPS project
 * http://ozlabs.org/~jk/projects/patchwork The patch home page