docs/7 - Contributing to crosstool-NG.txt
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Aug 02 18:28:10 2011 +0200 (2011-08-02)
changeset 2590 b64cfb67944e
parent 2077 b11117cdfdf7
child 2700 e8d25b041de5
permissions -rw-r--r--
scripts/functions: svn retrieval first tries the mirror for tarballs

The svn download helper looks for the local tarballs dir to see if it
can find a pre-downloaded tarball, and if it does not find it, does
the actual fetch to upstream via svn.

In the process, it does not even try to get a tarball from the local
mirror, which can be useful if the mirror has been pre-populated
manually (or with a previously downloaded tree).

Fake a tarball get with the standard tarball-download helper, but
without specifying any upstream URL, which makes the helper directly
try the LAN mirror.

Of course, if no mirror is specified, no URL wil be available, and
the standard svn retrieval will kick in.

Reported-by: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@2076
     1
File.........: 7 - Contributing to crosstool-NG.txt
antony@2563
     2
Copyright....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
yann@2076
     3
License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
yann@2076
     4
yann@2076
     5
yann@2076
     6
Contributing to crosstool-NG  /
yann@2076
     7
_____________________________/
yann@2076
     8
yann@2076
     9
yann@2076
    10
Sending a bug report |
yann@2076
    11
---------------------+
yann@2076
    12
yann@2076
    13
If you need to send a bug report, please send a mail with subject
yann@2076
    14
prefixed with "[CT_NG]" with to following destinations:
yann@2076
    15
    TO: yann.morin.1998 (at) anciens.enib.fr
yann@2076
    16
    CC: crossgcc (at) sourceware.org
yann@2076
    17
yann@2076
    18
yann@2076
    19
Sending patches |
yann@2076
    20
----------------+
yann@2076
    21
yann@2076
    22
If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
yann@2076
    23
yann@2076
    24
Patches should come with the appropriate SoB line. A SoB line is typically
yann@2076
    25
something like:
yann@2076
    26
   Signed-off-by: John DOE <john.doe@somewhere.net>
yann@2076
    27
yann@2076
    28
The SoB line is clearly described in Documentation/SubmittingPatches , section
yann@2076
    29
12, of your favourite Linux kernel source tree.
yann@2076
    30
yann@2076
    31
yann@2076
    32
For larger or more frequent contributions, mercurial should be used.
yann@2077
    33
There is a nice, complete and step-by-step tutorial in section 'C'.