This is the mail archive of the
mailing list for the binutils project.
Re: A Proposal to Move to Git
- From: Doug Evans <dje at google dot com>
- To: Binutils <binutils at sourceware dot org>
- Cc: gdb <gdb at sourceware dot org>
- Date: Fri, 23 Aug 2013 17:27:30 -0700
- Subject: Re: A Proposal to Move to Git
- References: <8738q4gj7a dot fsf at fleche dot redhat dot com> <201308222010 dot r7MKAljG013904 at glazunov dot sibelius dot xs4all dot nl> <87wqnda0tm dot fsf at fleche dot redhat dot com> <CAMe9rOr1ivRrGs2GtJU3cXgYJAzEx-wdatuzoY9NBDmh4jJqpg at mail dot gmail dot com> <87siy070su dot fsf at dod dot no>
On Fri, Aug 23, 2013 at 10:51 AM, Steinar Bang <email@example.com> wrote:
>>>>>> "H.J. Lu" <firstname.lastname@example.org>:
>> I assume git repo has both binutils and gdb. Is that possible to only
>> checkout binutils portion?
> Not as such. There is something similar called sparse checkouts.
> Eg. if your source is organized like
> you can opt to checkout only
> in your working directory.
> But it still will be organized as a binutils/ subdirectory at the top
> Ie. if you clone your binutils-only version of gdb+binutils like so
> git clone git://somegitrepo.org/gdbbinutils.git binutils
> you will have to do
> cd binutils/binutils
> to get to he interesting stuff...
> Also the "user interface" for sparse checkouts kinda sucks:
> - You set a git property
> - You add lines to a text file saying what should be checked out
> - You either do an initial checkout, or you use the little used command
> git-read-tree to update the working directory
> After this, git can be used normally (merge, add, commit, push).
> If disk usage is an issue, I guess it could be useful...? You would
> still have the entire git repo, though.
Not that this is necessarily one of HJ's issues, but it's too bad
"binutils" is both the name of the package and a directory within it.
Otherwise I can imagine all-binutils, install-binutils, check-binutils
in the top level makefile doing the right thing (e.g. being wrappers
for all-gas+all-ld+..., etc.).