From: Iain Sandoe <iain@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Binutils <binutils@sourceware.org>, GDB Development <gdb@sourceware.org>
Subject: Re: src.git test repository
Date: Tue, 08 Oct 2013 23:28:00 -0000 [thread overview]
Message-ID: <B20AE810-D9BE-43C6-A9DF-55919C85834E@codesourcery.com> (raw)
In-Reply-To: <87mwmlkojs.fsf@fleche.redhat.com>
Hi Tom,
thanks for doing this!
On 7 Oct 2013, at 17:56, Tom Tromey wrote:
> HJ> I noticed that binutils-2_24-branch only has binutils source.
> HJ> How will binutils-2_25-branch be made? Will it include gdb
> HJ> source?
>
> It's up to the binutils developers.
>
> What I recommend is branching the whole repository and then doing
> tarball releases of a subset of the branch, using the usual src-release
> mechanism.
I had a go this evening (with success) doing the following:
cloned src
built a sparse checkout by hand for 'binutils'
and built a cross from x86-64-darwin12 -> powerpc-linux-gnu
All seems OK, but I think I lost track of where the discussion had got to on sparse checkouts, building the .git/info/sparse-checkout file by hand is tedious.
somewhere to put the recipes/defaults corresponding to the existing checkouts would be handy.
or did I miss it?
Iain
next prev parent reply other threads:[~2013-10-08 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 15:19 Tom Tromey
2013-10-07 16:24 ` Eli Zaretskii
2013-10-07 16:53 ` Tom Tromey
2013-10-07 16:43 ` H.J. Lu
2013-10-07 16:56 ` Tom Tromey
2013-10-08 23:28 ` Iain Sandoe [this message]
2013-10-09 1:29 ` Tom Tromey
2013-10-09 5:15 ` Iain Sandoe
2013-10-09 21:04 ` Tom Tromey
2013-10-10 5:13 ` Joel Brobecker
2013-10-10 13:22 ` Tom Tromey
2013-10-10 13:44 ` Joel Brobecker
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=B20AE810-D9BE-43C6-A9DF-55919C85834E@codesourcery.com \
--to=iain@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.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).