Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Binutils <binutils@sourceware.org>
Cc: gdb <gdb@sourceware.org>
Subject: Re: A Proposal to Move to Git
Date: Sat, 24 Aug 2013 00:27:00 -0000	[thread overview]
Message-ID: <CADPb22R2uJPioSgnkSntzDARUstiWRELH139ymgFd6PgO9nX_A@mail.gmail.com> (raw)
In-Reply-To: <87siy070su.fsf@dod.no>

On Fri, Aug 23, 2013 at 10:51 AM, Steinar Bang <sb@dod.no> wrote:
>>>>>> "H.J. Lu" <hjl.tools@gmail.com>:
>
>> 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
>  binutils/
>  gdb/
> you can opt to checkout only
>  binutils/
> in your working directory.
>
> But it still will be organized as a binutils/ subdirectory at the top
> level.
>
> 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.).


  parent reply	other threads:[~2013-08-24  0:27 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 21:12 Tom Tromey
2013-08-20 21:16 ` Andrew Pinski
2013-08-20 21:26   ` Joseph S. Myers
2013-08-20 21:19 ` Joel Brobecker
2013-08-20 21:21 ` Paul_Koning
2013-08-20 22:59 ` Phil Muldoon
2013-08-21 15:05 ` Eli Zaretskii
2013-08-21 15:32   ` Andreas Schwab
2013-08-21 15:54     ` Eli Zaretskii
2013-08-26  8:05       ` Andreas Schwab
2013-08-21 18:40   ` Steinar Bang
2013-08-21 20:05     ` Eli Zaretskii
2013-08-21 20:38       ` Andreas Schwab
2013-08-22 18:56   ` Florian Weimer
2013-08-21 15:38 ` Steve Ellcey
2013-08-21 15:50   ` Joel Brobecker
2013-08-22  6:10     ` Tristan Gingold
2013-08-22 14:16   ` Richard Earnshaw
2013-08-22 14:25     ` Joel Brobecker
2013-08-22 14:39       ` Fred Cooke
2013-08-22 20:10 ` Mark Kettenis
2013-08-22 20:21   ` Fred Cooke
2013-08-22 20:22   ` David Miller
2013-08-22 20:48     ` Andrew Pinski
2013-08-22 21:07   ` Andreas Schwab
2013-08-22 21:10   ` Tom Tromey
2013-08-23 15:40     ` H.J. Lu
2013-08-23 15:55       ` Joel Brobecker
2013-08-23 16:03         ` Paul_Koning
2013-08-23 16:05           ` H.J. Lu
2013-08-26 12:37             ` NightStrike
     [not found]               ` <upzc38pvcv1w.fsf@dod.no>
2013-08-27 16:21                 ` asmwarrior
2013-08-23 16:03         ` H.J. Lu
2013-08-23 16:09           ` Joel Brobecker
2013-08-23 16:24       ` Matt Rice
2013-08-23 16:37         ` H.J. Lu
2013-08-23 16:47           ` Matt Rice
2013-08-23 17:01             ` H.J. Lu
     [not found]       ` <87siy070su.fsf@dod.no>
2013-08-24  0:27         ` Doug Evans [this message]
2013-08-22 23:55   ` Alan Modra
2013-08-30 22:58 ` Hans-Peter Nilsson
2013-08-30 23:37   ` Joseph S. Myers
2013-08-31  2:05     ` Hans-Peter Nilsson
2013-08-31 16:58       ` Joseph S. Myers
2013-09-04 16:55       ` Doug Evans

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=CADPb22R2uJPioSgnkSntzDARUstiWRELH139ymgFd6PgO9nX_A@mail.gmail.com \
    --to=dje@google.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    /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