public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Binutils Development <binutils@sourceware.org>,
	GDB Development <gdb@sourceware.org>
Subject: Re: src.git test repository
Date: Mon, 07 Oct 2013 16:43:00 -0000	[thread overview]
Message-ID: <CAMe9rOrxoQ_CHpojn_hB03fkJjPXrfrSKsV3VbtQG99g6s7DdQ@mail.gmail.com> (raw)
In-Reply-To: <87y565m7ma.fsf@fleche.redhat.com>

On Mon, Oct 7, 2013 at 8:19 AM, Tom Tromey <tromey@redhat.com> wrote:
> I've made a src.git test repository for testing.  Please try it out.
>
> The new repository came in much smaller than I thought: 196M.
> My checked-out tree is 506M.
>
> You can get it in the usual ways.  I used:
>
>     git clone ssh://sourceware.org/git/src.git
>
> I think "git://" works as well; not sure about http transport.
>
> Note that I made this repository last week, before I did most of the
> requested email address updates.
>
>
> This repository was made by a rather complicated process.  I stitched
> together Pedro's git repository holding very old (pre-devo) gdb
> releases, a somewhat edited snapshot of devo that I got from Ian and
> Nick, and of course "src".
>

I noticed that binutils-2_24-branch only has binutils source.
How will binutils-2_25-branch be made?  Will it include gdb
source?


H.J.

  parent reply	other threads:[~2013-10-07 16:43 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 [this message]
2013-10-07 16:56   ` Tom Tromey
2013-10-08 23:28     ` Iain Sandoe
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=CAMe9rOrxoQ_CHpojn_hB03fkJjPXrfrSKsV3VbtQG99g6s7DdQ@mail.gmail.com \
    --to=hjl.tools@gmail.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).