public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Bernie Innocenti <bernie@codewiz.org>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: git mirror repacked, new branches
Date: Wed, 18 Nov 2009 18:39:00 -0000	[thread overview]
Message-ID: <6dc9ffc80911181038q29e4334fo510d9778d9428d1e@mail.gmail.com> (raw)
In-Reply-To: <1258567789.3371.26.camel@giskard>

On Wed, Nov 18, 2009 at 10:09 AM, Bernie Innocenti <bernie@codewiz.org> wrote:
> El Wed, 18-11-2009 a las 07:13 -0800, H.J. Lu escribió:
>> On Sun, Nov 15, 2009 at 4:32 PM, Bernie Innocenti <bernie@codewiz.org> wrote:
>> > I repacked our (un)official git mirror (http://gcc.gnu.org/git) with
>> >
>> >  git repack -a -d -f --window=100 --depth=100 --window-memory=2g
>> >
>> > The pack is now 600MB, which is a bit scary, but still manageable.
>> > Mysteriously, cloning this repo yields a smaller pack of just 519MB,
>> > which still contains all the branches. It was probably caused by entries
>> > in the reflog, which I have now disabled.
>> >
>> > As an additional bonus, I've added refs for all the current branches tom
>> > make them visible in gitweb and easier to clone.
>>
>> Most of vendor branches are wrong. For example, there are many branches
>> under branches/redhat. But I only see one redhat branch in git.
>
> I guess git-svn does not cope automatically with nested subdirs in
> banches/.

If nested subdirs in banches/ aren't handled properly, shouldn't we avoid
putting them in git mirror?

> One could manually select them by passing multiple --branches options.
> For our case, the man page shows how to map those branches to separate
> namespaces:
>
>  branches = stable/*:refs/remotes/svn/stable/*
>  branches = debug/*:refs/remotes/svn/debug/*
>
>
> Properly handling vendor branches would be a requisite step for a real
> migration to git. For now, I'd rather be lazy and delay this work until
> someone asks for it.
>
>
>> BTW, I can't pull new changes from the new master into my local git branches
>> which are based on the old master.
>
> This is unexpected. Repacking doesn't change any SHA1, and I haven't
> touched any of the existing branches. What error do you get from pull?
>

Oops. Pilot error.


-- 
H.J.

  reply	other threads:[~2009-11-18 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16  0:33 Bernie Innocenti
2009-11-18 15:14 ` H.J. Lu
2009-11-18 18:10   ` Bernie Innocenti
2009-11-18 18:39     ` H.J. Lu [this message]
2009-11-18 20:03       ` Bernie Innocenti
2009-11-19 22:46         ` Jason Merrill
2009-11-20  2:51           ` Bernie Innocenti
2009-11-19  5:12     ` Alexandre Oliva
2009-11-19  5:25       ` Bernie Innocenti

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=6dc9ffc80911181038q29e4334fo510d9778d9428d1e@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=bernie@codewiz.org \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).