URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [or1ksim/] [MAINTAINERS] - Blame information for rev 867

Go to most recent revision | Details | Compare with Previous | View Log


                             OR1KSIM MAINTAINERS
                             ===================
 
This file contains information about people who are permitted to make changes
to various parts of the compiler and associated libraries.
 
Please do not contact the people in this file directly to report problems in
Or1ksim.
 
For general information about Or1ksim, post to both OpenRISC mailing lists:
 
  openrisc@lists.openrisc.net
  openrisc@lists.opencores.org
 
(yes we do mean crosspost - they have disjoint sets of readers).
 
To report problems with Or1ksim, please visit:
 
  http://bugzilla.opencores.org/
 
 
Patch submission process
========================
 
The following process applies to both the SVN HEAD and release branches.
 
* Submit the patch to both OpenRISC mailing lists a diff against current SVN
  HEAD.
  - make sure you put the patch inline.
 
* Deal with any review comments.
 
* when the patch is approved (by any maintainer), anyone with
  write-after-approval permission to the SVN repository may commit the patch.
 
Note in particular a patch will not be accepted if the resulting code does not
pass "make distcheck".
 
Committing to private branches by the owner of that private branch needs no
approval process. Merge of that private branch into either SVN HEAD or a
release branch should follow the patch submission process above.
 
 
MAINTAINER
==========
 
The following people may approve patches to Or1ksim
 
  Julius Baxter                          julius@opencores.org
  Jeremy Bennett                         jeremybennett@opencores.org
 
 
WRITE AFTER APPROVAL
====================
 
The following people may commit patches after approval by a MAINTAINER
 
  Julius Baxter                          julius@opencores.org
  Jeremy Bennett                         jeremybennett@opencores.org
 
 
OBVIOUS PATCHES
===============
 
Anyone with write-after-approval permission may commit "obvious" patches. For
example trivial typos.
 
Such patches should be posted after the event to both mailing lists (with the
tag [OBV] in teh subject line).

Line No.	Rev	Author	Line
1	792	jeremybenn	`OR1KSIM MAINTAINERS`
2			`===================`
3
4			`This file contains information about people who are permitted to make changes`
5			`to various parts of the compiler and associated libraries.`
6
7			`Please do not contact the people in this file directly to report problems in`
8			`Or1ksim.`
9
10			`For general information about Or1ksim, post to both OpenRISC mailing lists:`
11
12			`openrisc@lists.openrisc.net`
13			`openrisc@lists.opencores.org`
14
15			`(yes we do mean crosspost - they have disjoint sets of readers).`
16
17			`To report problems with Or1ksim, please visit:`
18
19			`http://bugzilla.opencores.org/`
20
21
22			`Patch submission process`
23			`========================`
24
25			`The following process applies to both the SVN HEAD and release branches.`
26
27			`* Submit the patch to both OpenRISC mailing lists a diff against current SVN`
28			`HEAD.`
29			`- make sure you put the patch inline.`
30
31			`* Deal with any review comments.`
32
33			`* when the patch is approved (by any maintainer), anyone with`
34			`write-after-approval permission to the SVN repository may commit the patch.`
35
36			`Note in particular a patch will not be accepted if the resulting code does not`
37			`pass "make distcheck".`
38
39			`Committing to private branches by the owner of that private branch needs no`
40			`approval process. Merge of that private branch into either SVN HEAD or a`
41			`release branch should follow the patch submission process above.`
42
43
44			`MAINTAINER`
45			`==========`
46
47			`The following people may approve patches to Or1ksim`
48
49	793	jeremybenn	`Julius Baxter julius@opencores.org`
50	792	jeremybenn	`Jeremy Bennett jeremybennett@opencores.org`
51
52
53			`WRITE AFTER APPROVAL`
54			`====================`
55
56			`The following people may commit patches after approval by a MAINTAINER`
57
58	793	jeremybenn	`Julius Baxter julius@opencores.org`
59	792	jeremybenn	`Jeremy Bennett jeremybennett@opencores.org`
60
61
62			`OBVIOUS PATCHES`
63			`===============`
64
65			`Anyone with write-after-approval permission may commit "obvious" patches. For`
66			`example trivial typos.`
67
68			`Such patches should be posted after the event to both mailing lists (with the`
69			`tag [OBV] in teh subject line).`

Browse

Tools

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [or1ksim/] [MAINTAINERS] - Blame information for rev 867