Syncing just the manifest branch by default - Chromium OS dev

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Syncing just the manifest branch by default
Received-SPF: pass (google.com: domain of kli...@chromium.org designates 209.85.223.178 as permitted sender) client-ip=209.85.223.178;
MIME-Version: 1.0
In-Reply-To: <CAK=2k1GdN2kjb_eCti_JbwXonqv4j0rtcMK5QNa5gqMDjdP...@mail.gmail.com>
References: <CAK=2k1GdN2kjb_eCti_JbwXonqv4j0rtcMK5QNa5gqMDjdP...@mail.gmail.com>
From: Jonathan Kliegman <kli...@chromium.org>
Date: Fri, 16 Nov 2012 01:58:04 -0500
Message-ID: <CAPQV+nPs93uCdbr-kKkcUGj60rDpg=evb0yLKNauK7cTB0H...@mail.gmail.com>
Subject: Re: [cros-dev] Syncing just the manifest branch by default
To: Brian Harring <ferri...@google.com>
Cc: Chromium OS dev <chromium-os-...@chromium.org>
Content-Type: multipart/alternative; boundary=14dae934071f544b2c04ce974b5d

--14dae934071f544b2c04ce974b5d
Content-Type: text/plain; charset=ISO-8859-1

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
>
>
>
>

--14dae934071f544b2c04ce974b5d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div style=3D"font-family:arial,helvetica,sans-serif;font-size:10pt"><br><d=
iv class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Nov 16,=
 2012 at 1:07 AM, Brian Harring <span dir=3D"ltr">&lt;<a href=3D"mailto:fer=
ri...@google.com" target=3D"_blank" class=3D"cremed">ferri...@google.com</a=
>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"font-family:arial,helvetica,sa=
ns-serif;font-size:10pt">Hola folks-<div><br>Currently, for all repo&#39;s =
except chromiumos-overlay, we pull down all branches for each git-repositor=
y. =A0This is actually is an additional 700MB or so for the private checkou=
ts- data that most people don&#39;t actually care about.<br>


<br>This is around 10%; anyone care if I suppress that, and make repo just =
sync the branches that the manifest specifics?<br></div></div></blockquote>=
<div>=A0Overall this seems a good way to save time - I think most of the ti=
me I&#39;m not looking at the other branches unless I&#39;m merging a backp=
ort and then I generally have a second checkout I use for that. =A0We&#39;d=
 want an easy way to still get those branches though.</div>

<div><br></div><div>Would I still be able to run &#39;git branch -r&#39; to=
 see the branches? =A0And just take a hit the first time I pulled one? =A0O=
r would I not even know they existed and have to do some tricks to pull the=
m?</div>

<div><br></div><div>Would it be possible to add a way to annotate the manif=
est with &quot;also sync these branches&quot; or to modify something in the=
 git metadata to do the equivalent? =A0I feel there are times (updating to =
new kernel versions) where people working in the tree would care about mult=
iple branches at once. =A0It&#39;d be nice to make things simpler in those =
cases.=A0</div>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"font-family:arial,helvetica,sa=
ns-serif;font-size:10pt"><div><br>~brian</div></div><span class=3D"HOEnZb">=
<font color=3D"#888888">

<p></p>

-- <br>
-- <br>
Chromium OS Developers mailing list: <a href=3D"mailto:chromium-os-dev@chro=
mium.org" target=3D"_blank" class=3D"cremed">chromium-os-...@chromium.org</=
a><br>
View archives, change email options, or unsubscribe: <br>
<a href=3D"http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=
=3Den" target=3D"_blank" class=3D"cremed">http://groups.google.com/a/chromi=
um.org/group/chromium-os-dev?hl=3Den</a><br>
=A0<br>
=A0<br>
=A0<br>
</font></span></blockquote></div><br></div></div>

--14dae934071f544b2c04ce974b5d--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
