Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home for chromium.org
« Groups Home
Message from discussion Syncing just the manifest branch by default
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jonathan Kliegman  
View profile  
 More options Nov 16 2012, 1:58 am
From: Jonathan Kliegman <kli...@chromium.org>
Date: Fri, 16 Nov 2012 01:58:04 -0500
Local: Fri, Nov 16 2012 1:58 am
Subject: Re: [cros-dev] Syncing just the manifest branch by default

On Fri, Nov 16, 2012 at 1:07 AM, Brian Harring <ferri...@google.com> wrote:
> Hola folks-

> Currently, for all repo's except chromiumos-overlay, we pull down all
> branches for each git-repository.  This is actually is an additional 700MB
> or so for the private checkouts- data that most people don't actually care
> about.

> This is around 10%; anyone care if I suppress that, and make repo just
> sync the branches that the manifest specifics?

 Overall this seems a good way to save time - I think most of the time I'm
not looking at the other branches unless I'm merging a backport and then I
generally have a second checkout I use for that.  We'd want an easy way to
still get those branches though.

Would I still be able to run 'git branch -r' to see the branches?  And just
take a hit the first time I pulled one?  Or would I not even know they
existed and have to do some tricks to pull them?

Would it be possible to add a way to annotate the manifest with "also sync
these branches" or to modify something in the git metadata to do the
equivalent?  I feel there are times (updating to new kernel versions) where
people working in the tree would care about multiple branches at once.
 It'd be nice to make things simpler in those cases.

> ~brian

> --
> --
> Chromium OS Developers mailing list: chromium-os-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.