Ignore:
Timestamp:
Feb 25, 2011, 9:26:54 PM (9 years ago)
Author:
Bruno Cornec
Message:
  • Update mindi-busybox to 1.18.3 to avoid problems with the tar command which is now failing on recent versions with busybox 1.7.3
File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2.2.9/mindi-busybox/docs/contributing.txt

    r821 r2725  
    1818
    1919
    20 Checkout the Latest Code from CVS
    21 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     20Checkout the Latest Code
     21~~~~~~~~~~~~~~~~~~~~~~~~
    2222
    2323This is a necessary first step. Please do not try to work with the last
     
    2626Don't make your work obsolete before you start!
    2727
    28 For information on how to check out Busybox from CVS, please look at the
     28For information on how to check out Busybox development tree, please look at the
    2929following links:
    3030
    31     http://busybox.net/cvs_anon.html
    32     http://busybox.net/cvs_howto.html
     31    http://busybox.net/source.html
    3332
    3433
     
    8887   filesystem under the sun. (fsck_minix.c and mkfs_minix.c are living on
    8988   borrowed time.) There are far too many of these tools out there.  Use
    90    the upstream version. Not everything has to be part of Busybox.
    91 
    92  - Any partitioning tools: Partitioning a device is typically done once and
    93    only once, and tools which do this generally do not need to reside on the
    94    target device (esp a flash device). If you need a partitioning tool, grab
    95    one (such as fdisk, sfdisk, or cfdisk from util-linux) and use that, but
    96    don't try to merge it into busybox. These are nasty and complex and we
    97    don't want to maintain them.
     89   the upstream version.  Rationale: bugs in these tools can destroy
     90   vast amounts of data.  Keeping up with filesystem format development
     91   is impractical (especially in the area of keeping fsck tool safe
     92   and up-to-date).
    9893
    9994 - Any disk, device, or media-specific tools: Use the -utils or -tools package
     
    10398   independent. Do not send us tools that cannot be used across multiple
    10499   platforms / arches.
    105 
    106  - Any daemons that are not essential to basic system operation. To date, only
    107    syslogd and klogd meet this requirement. We do not need a web server, an
    108    ftp daemon, a dhcp server, a mail transport agent or a dns resolver. If you
    109    need one of those, you are welcome to ask the folks on the mailing list for
    110    recommendations, but please don't bloat up Busybox with any of these.
    111100
    112101
     
    136125
    137126    $ date
    138     llegal instruction
     127    Illegal instruction
    139128
    140129    I am using Debian unstable, kernel version 2.4.19-rmk1 on an Netwinder,
    141     and the latest uClibc from CVS.  Thanks for the wonderful program!
     130    and the latest uClibc from CVS.
    142131
    143132    -Diligent
     
    200189These are dirty jobs, but somebody's gotta do 'em.
    201190
    202  - Converting applets to use getopt() for option processing. Type 'find -name
    203    '*.c'|grep -L getopt' to get a listing of the applets that currently don't
    204    use getopt. If a .c file processes no options, it should have a line that
    205    reads: /* no options, no getopt */ somewhere in the file.
    206 
    207  - Replace any "naked" calls to malloc, calloc, realloc, str[n]dup, fopen with
    208    the x* equivalents found in libbb/xfuncs.c.
    209 
    210191 - Security audits:
    211192   http://www.securityfocus.com/popups/forums/secprog/intro.shtml
     
    236217Other useful links:
    237218
    238  - the comp.lang.c FAQ: http://web.onetelnet.ch/~twolf/tw/c/index.html#Sources
     219 - the comp.lang.c FAQ: http://home.datacomm.ch/t_wolf/tw/c/index.html#Sources
    239220
    240221
     
    249230~~~~~~~~~~~~~~
    250231
    251 If you've got anonymous CVS access set up, making a patch is simple. Just make
    252 sure you're in the busybox/ directory and type 'cvs diff -bwu > mychanges.patch'.
     232If you've got anonymous Git access set up, making a patch is simple. Just make
     233sure you're in the busybox/ directory and type:
     234
     235    git diff -b -w > mychanges.patch
     236
    253237You can send the resulting .patch file to the mailing list with a description
    254238of what it does. (But not before you test it! See the next section for some
     
    258242Also, feel free to help test other people's patches and reply to them with
    259243comments. You can apply a patch by saving it into your busybox/ directory and
    260 typing 'patch < mychanges.patch'. Then you can recompile, see if it runs, test
    261 if it works as advertised, and post your findings to the mailing list.
     244typing:
     245
     246    patch -p1 < mychanges.patch
     247
     248Then you can recompile, see if it runs, test if it works as advertised, and
     249post your findings to the mailing list.
    262250
    263251NOTE: Please do not include extraneous or irrelevant changes in your patches.
     
    272260
    273261It's considered good form to test your new feature before you submit a patch
    274 to the mailing list, and especially before you commit a change to CVS. Here
     262to the mailing list, and especially before you push a change to Git. Here
    275263are some guidelines on how to test your changes.
    276264
     
    368356
    369357We've made strident efforts to put a useful "collaboration" infrastructure in
    370 place in the form of mailing lists, the bug tracking system, and CVS. Please
     358place in the form of mailing lists, the bug tracking system, and Git. Please
    371359use these resources.
    372360
     
    393381
    394382
    395 Committing Changes to CVS
    396 -------------------------
     383Pushing Changes to Git
     384----------------------
    397385
    398386If you submit several patches that demonstrate that you are a skilled and wise
    399 coder, you may be invited to become a committer, thus enabling you to commit
    400 changes directly to CVS. This is nice because you don't have to wait for
    401 someone else to commit your change for you, you can just do it yourself.
     387coder, you may be invited to become a committer, thus enabling you to push
     388changes directly to Git. This is nice because you don't have to wait for
     389someone else to push your change for you, you can just do it yourself.
    402390
    403391But note that this is a privilege that comes with some responsibilities. You
    404 should test your changes before you commit them. You should also talk to an
     392should test your changes before you push them. You should also talk to an
    405393applet maintainer before you make any kind of sweeping changes to somebody
    406394else's code. Big changes should still go to the mailing list first. Remember,
    407395being wise, polite, and discreet is more important than being clever.
    408396
    409 
    410 When To Commit
    411 ~~~~~~~~~~~~~~
    412 
    413 Generally, you should feel free to commit a change if:
     397For more information on Git push access, see:
     398
     399    http://busybox.net/developer.html
     400
     401
     402When To Push
     403~~~~~~~~~~~~
     404
     405Generally, you should feel free to push a change if:
    414406
    415407 - Your changes are small and don't touch many files
     
    418410 - It's obviously the Right Thing
    419411
    420 The more of the above are true, the better it is to just commit a change
    421 directly to CVS.
    422 
    423 
    424 When Not To Commit
    425 ~~~~~~~~~~~~~~~~~~
    426 
    427 Even if you have commit rights, you should probably still post a patch to the
     412The more of the above are true, the better it is to just push a change
     413directly to Git.
     414
     415
     416When Not To Push
     417~~~~~~~~~~~~~~~~
     418
     419Even if you have push access, you should probably still post a patch to the
    428420mailing list if:
    429421
     
    434426
    435427The more of the above are true, the better it is to post a patch to the
    436 mailing list instead of committing.
     428mailing list instead of pushing.
    437429
    438430
     
    446438good-natured bunch and will work with you to help get your patches into shape
    447439or help you make contributions.
    448 
    449 
Note: See TracChangeset for help on using the changeset viewer.