Changes between Version 6 and Version 7 of Developer/Removing_a_BSP


Ignore:
Timestamp:
Dec 8, 2015, 6:49:13 AM (4 years ago)
Author:
Sebastian Huber
Comment:

Use only one patch for a BSP removal.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Removing_a_BSP

    v6 v7  
    3030  cd .../c/src/lib/libbsp/@ARCHITECTURE@
    3131  git rm -f @BSP_FAMILY@
    32   git add .
     32}}}
     33
     34''Regenerate the acinclude.m4 file in c/src/libbsp/@ARCHITECTURE@''
     35
     36{{{
     37../../../../../bootstrap
     38git add acinclude.m4
     39}}}
     40
     41Now, commit it.
     42
     43{{{
    3344  git commit
    3445}}}
     
    3950@ARCHITECTURE@/@BSP_FAMILY@: Remove
    4051
    41 updates #NNNN.
     52Close #NNNN.
    4253}}}
    4354
    4455where NNNN is the ticket number for the ticket filed earlier.
    4556
    46 ''Regenerate the acinclude.m4 file in c/src/libbsp/@ARCHITECTURE@''
     57At this point, you should have a git branch named "am" which one patch. Send this patch to the RTEMS development mailing list. The lines at the bottom of the commit messages will automatically close the ticket when the patch is committed.
    4758
    48 {{{
    49 ../../../../../bootstrap
    50 git add acinclude.m4
    51 git commit
    52 }}}
    53 
    54 The commit message for the above should be something like:
    55 
    56 {{{
    57 @ARCHITECTURE@/acinclude.m4: Regenerate to remove @BSP_FAMILY@
    58 
    59 closes #NNNN.
    60 }}}
    61 
    62 where NNNN is the ticket number for the ticket filed earlier.
    63 
    64 At this point, you should have a git branch named "am" which has two patches. Send these patches to the RTEMS development mailing list. The lines at the bottom of the commit messages will automatically update and close the ticket when the patch is committed.
     59Some BSPs use code in c/src/libcpu/@ARCHITECTURE@.  Look for *.rel files in the Makefile.am of the BSP.  In doubt, ask on the mailing list.
    6560
    6661== Other Possible References to @BSP@ ==