From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Titus von Boxberg <titus@v9g.de>
Subject: Re: [PATCH 0 of 5] Several patches for OSX,uClibc,gdb-6.8
Date: Sun, 21 Aug 2011 22:53:00 -0000 [thread overview]
Message-ID: <201108220053.09518.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <201108220021.58954.yann.morin.1998@anciens.enib.fr>
Titus, All,
On Monday 22 August 2011 00:21:58 Yann E. MORIN wrote:
> On Sunday 21 August 2011 15:09:00 Titus von Boxberg wrote:
> > Yann, all,
> >
> > this patch series corrects various bugs when building on OSX.
>
> Looks good.
Also, could you recategorise the changesets:
patch 1/5: configure: fix --with-prog=[...]
patch 2/5: configure: require libtoolise, create wrapper
patch 3/5: libc/uClibc: portability fixes to install_headers
patch 4/5: docs: document usage with Xcode 4.1
patch 5/5: debug/gdb: correct compilation error when stpcpy is a define
The global rule is:
- when changing a component, the prefix is: categroy/component
for example:
kernel/linux: add blabla
arch/arm: do foo bar
debug/gdb: buzify the bazel
libc/uClibc: check the stuff
complibs/ppl: do that foolish stuff again
- when changing configure (and the correspondiong stuff in Makefile.in)
the prefix is simply: configure
for example:
configure: fix blabla, require foobar
- when changing stuff in kconfig, the prefix should be: kconfig
optionally, the frontend can be specified. eg.:
kconfig: fix bla bla
kconfig/mconf: show bar buz
kconfig/nconf: hide bar buz
- other prefixes could be:
config : for changes to the infrastructure in the config/ dir
scripts : for changes to the infrastructure in the scripts/ dir
samples : for changes in the samples/ dir
docs : for changes to the documentation
Deviations to the rule can apply, of course, but that should be the exception
rather than the rule.
No, this is not documented, I'll do it soon (probably tomorrow).
Thanks again for looking into that! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2011-08-21 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 13:13 Titus von Boxberg
2011-08-21 13:13 ` [PATCH 1 of 5] configure: correct check_for Titus von Boxberg
2011-08-21 13:14 ` [PATCH 3 of 5] patches/uClibc-0.9.30: install_headers build step portable to OSX 10.7 Titus von Boxberg
2011-08-21 13:14 ` [PATCH 4 of 5] docs/Using on MacOS: Document usage with Xcode 4.1 Titus von Boxberg
2011-08-21 13:14 ` [PATCH 2 of 5] main: need path to libtoolize Titus von Boxberg
2011-08-21 13:21 ` [PATCH 5 of 5] patches/gdb/6.8: correct compilation error when stpcpy is a define Titus von Boxberg
2011-08-21 22:22 ` [PATCH 0 of 5] Several patches for OSX,uClibc,gdb-6.8 Yann E. MORIN
2011-08-21 22:53 ` Yann E. MORIN [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201108220053.09518.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=titus@v9g.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).