From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Mau Z <zmau1962@gmail.com>
Cc: crossgcc@sourceware.org
Subject: Re: Q: Any revision control tips ?
Date: Mon, 30 Dec 2013 23:03:00 -0000 [thread overview]
Message-ID: <20131230230307.GC3472@free.fr> (raw)
In-Reply-To: <CAPFcPTJ3J06SbwdsUnKQQ52Vigj8WBQGOfn+PXzOq4tPmqSPeQ@mail.gmail.com>
Mau, All,
On 2013-12-31 00:26 +0200, Mau Z spake thusly:
> So, at the end of the succesfull build, I did "du -h" and got 5.X GB of data.
>
> What should I keep in a revision control system ?
> Any constructive advices/tips ?
Just keep the crostool-NG sources in revision control, plus your ct-ng
configuration:
ct-ng saveconfig
This will create a subdir 'samples/${CT_TARGET}' in the current directory,
that copntains the crosstool-NG configuration.
You can later use that same configuration again, by calling:
ct-ng "name-of-your-configuration"
where "name-of-your-configuration" is just the tuple (aka ${CT_TARGET}).
You can even see the existing configurations bundled with ct-ng:
ct-ng list-samples
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
next prev parent reply other threads:[~2013-12-30 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 22:26 Mau Z
2013-12-30 23:03 ` Yann E. MORIN [this message]
2013-12-30 23:07 ` Mau Z
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=20131230230307.GC3472@free.fr \
--to=yann.morin.1998@free.fr \
--cc=crossgcc@sourceware.org \
--cc=zmau1962@gmail.com \
/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).