manifests/default.xml is not on the master branch
Kunjal
We need to update default.xml file to update the fetch location.
When I execute "git show-branch" command at .repo/manifests/ directory
It is not showing master branch but showing [default]. what is the
meaning of that?
I need default.xml file on master branch so when someone sync repo
content to worksapce, they get updated default.xml file.
Any help is appriciated.
Thanks
Kunjal
Shawn Pearce
sal de la tierra
my searches this is the only the discussion which addresses the
author's question, and I have the same question.
Thanks
Emil Sit
> There are many threads on here about creating a mirror repository and
> updating the URL. Look for one of those.
threads.
Anyway, are there any plans to separate the specification of the
source
from the manifest xml file? For example, one could imagine that:
repo init -u git://android.git.kernel.org/platform/manifest.git
would have repo parse the -u argument to determine that the fetch
parameter should be git://android.git.kernel.org/. If someone has a
mirror,
their internal clients would run (e.g.):
repo init -u git://git.omapzoom.org/platform/manifest.git
and instead of the mirror maintainer having to branch/edit
manifest.git,
things would "just work" with fetch=git://git.omapzoom.org/.
In such a scheme, a mirror maintainer could obviously branch away
from master if they want to in order to add chipset packages or
other vendor extensions.
Would such a system work?
Shawn Pearce
>
> On Jul 24, 9:59 am, Shawn Pearce <s...@google.com> wrote:
>> There are many threads on here about creating a mirror repository and
>> updating the URL. Look for one of those.
>
> Oddly, searching for "mirror" in this group only reveals three
> threads.
Bad search engine? *sigh* I also can't find anything in the
archives. Maybe I shouldn't say that given who signs my paycheck.
> Anyway, are there any plans to separate the specification of the
> source
> from the manifest xml file? For example, one could imagine that:
> repo init -u git://android.git.kernel.org/platform/manifest.git
> would have repo parse the -u argument to determine that the fetch
> parameter should be git://android.git.kernel.org/.
I've wanted to make this sort of improvement, but its been difficult
with the way repo has been structured internally. It might be easier
in the current master version, which hasn't been signed and tagged
yet, but mostly supports using git submodules rather than an XML
manifest format. I know some folks just tell users to insert
url.insteadof lines in their ~/.gitconfig, and let git rewrite the URL
during fetch, but its not as friendly as actually doing the resolve in
repo.
Sure, what you ask for is possible, and might not be *that* hard to
do, but its so far down on my current priority list that practically I
won't be getting to it anytime soon. I know I say that on here
sometimes, and then I just *poof* add the feature anyway. This is
probably one I won't do anytime soon, there is a workaround available
(clone the manifest, edit it, push the edit back to your mirror of
it). If someone else proposes patches, I'll consider them.
Jey Michael
>
> On Tue, Aug 4, 2009 at 20:57, Emil Sit<s...@vmware.com> wrote:
>>
>> On Jul 24, 9:59 am, Shawn Pearce <s...@google.com> wrote:
>>> There are many threads on here about creating a mirror repository and
>>> updating the URL. Look for one of those.
>>
>> Oddly, searching for "mirror" in this group only reveals three
>> threads.
>
> Bad search engine? *sigh* I also can't find anything in the
> archives. Maybe I shouldn't say that given who signs my paycheck.
Easy on the signer :-) Search on my gmail worked fine, and here are
the results.
http://groups.google.com/group/repo-discuss/browse_thread/thread/8f7fd6188aec1a0c/82b29766d18843af
http://groups.google.com/group/repo-discuss/browse_thread/thread/8246f04ca098a44f/c086f88c0a2d4bf8
http://groups.google.com/group/repo-discuss/browse_thread/thread/824611be1c9ed6b9/4235318266939aa2
http://groups.google.com/group/repo-discuss/browse_thread/thread/639d60701c55554c/fa4c84491d7dd6f7
http://groups.google.com/group/repo-discuss/browse_thread/thread/67fdbba9619084/7ba8f714fa06ab1f
http://groups.google.com/group/repo-discuss/browse_thread/thread/9f33cdf5d73312eb/fe450ebd8e9c0ce7
-Jey
PS: The problem is in "search in this group." "Search all groups" is
cumbersome but works.
Emil Sit
> sometimes, and then I just *poof* add the feature anyway. This is
> probably one I won't do anytime soon, there is a workaround available
> (clone the manifest, edit it, push the edit back to your mirror of
> it). If someone else proposes patches, I'll consider them.
want to either track different branches in the upstream, or
you want to try older versions---you have to have a custom
branch for each branch/commit you want to sync to.
Using submodules with a relative URL would perhaps obviate the
need for this? What's the time-table for moving the main manifest
to submodules?
Thanks.
Jey
On Aug 5, 11:40 am, Jey Michael <jey.mich...@gmail.com> wrote:
> On Wed, Aug 5, 2009 at 7:27 AM, Shawn Pearce<s...@google.com> wrote:
>
> > On Tue, Aug 4, 2009 at 20:57, Emil Sit<s...@vmware.com> wrote:
>
> >> On Jul 24, 9:59 am, Shawn Pearce <s...@google.com> wrote:
> >>> There are many threads on here about creating a mirror repository and
> >>> updating the URL. Look for one of those.
>
> >> Oddly, searching for "mirror" in this group only reveals three
> >> threads.
>
> > Bad search engine? *sigh* I also can't find anything in the
> > archives. Maybe I shouldn't say that given who signs my paycheck.
>
>
> PS: The problem is in "search in this group." "Search all groups" is
> cumbersome but works.
For other groups, "Search in this group" seems to work fine. This
search problem seems to exist only for the repo-discuss group.
My theory is that the setup for this group is a little different
(posts go to archives sooner?, non-searchable archives?) from the
rest. Is that the case, Shawn?
-Jey