search

BasavarajMM / git-repo

Automatically exported from code.google.com/p/git-repo
Apache License 2.0
0 stars 0 forks source link

'repo manifest -o -' does not include all existing attributes from the .repo/manifest.xml #164

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Affected Version: v1.12.4 also tried v1.12.13
Environment: Linux Ubuntu 64-bit

What steps will reproduce the problem?
1. Have a manifest.xml that contains project attributes like 'upstream' or 
'sync_c'
2. Run 'repo manifest -o -' to make a manifest
3. Look at the manifest, the additional attributes are not in the output.

I expected to see that all attributes would be transferred to the made 
manifest.  Instead, only 'name', 'path', 'revision', and 'remote' are present.

Original issue reported on code.google.com by avec...@motorola.com on 28 Mar 2014 at 9:10

GoogleCodeExporter commented 8 years ago 
The 'upmerge' attribute to be retained is especially important when the 
revision is a SHA1, but the repo is usually synced from a different branch than 
the default.

Original comment by avec...@motorola.com on 28 Mar 2014 at 9:14

GoogleCodeExporter commented 8 years ago 
In my case, the manifest contains some repos that are using SHA1 revisions and 
upmerge is set, but other repos are using the default.  The manifest is also 
using the <include> to include other manifests.

I don't want the overhead of syncing the entire manifest to be able to use 
'repo manifest -r -o -' to get the upmerge settings.

My request is: For 'repo manifest' without '-r' to create a single manifest 
that traverses the <include> tags and still contain the amount of data in the 
original manifest(s).

Original comment by avec...@motorola.com on 11 Apr 2014 at 8:07

GoogleCodeExporter commented 8 years ago 
Hi,

Please can you provide a manifest file with Upstream or Sync_c attributes, that 
would help to reproduce the issue.

Original comment by neemish...@gmail.com on 25 Jun 2014 at 10:03

GoogleCodeExporter commented 8 years ago 
Please see the attached manifest

When you run 'repo manifest -o -' on this, it will remove the 'upstream' and 
'sync_c' even if the upstream is not the default revision.

I noticed if the 'path' and 'name' are the same, the 'path' is also removed, at 
least this is easily detectable as it is common manifest practice.

Original comment by avec...@motorola.com on 25 Jun 2014 at 3:12

Attachments:

GoogleCodeExporter commented 8 years ago 
https://gerrit-review.googlesource.com/#/c/58630/

Original comment by david.pu...@sonymobile.com on 16 Jul 2014 at 9:21

GoogleCodeExporter commented 8 years ago 
'sync-c' attribute should be used in place of 'sync_c' in the manifest.xml.

Change uploaded to fix the 'upstream' attribute -
https://gerrit-review.googlesource.com/#/c/58630/

Original comment by mani.cha...@tcs.com on 16 Jul 2014 at 9:22

GoogleCodeExporter commented 8 years ago 
Thank you.  Please also update the manifest help then as it states 'sync_c' and 
'sync_s', which is why I used it instead of 'sync-c'

repo help manifest

Attribute `sync_c`: Set to true to only sync the given Git branch
(specified in the `revision` attribute) rather than the whole ref space.

Attribute `sync_s`: Set to true to also sync sub-projects.

Original comment by avec...@motorola.com on 16 Jul 2014 at 3:24

GoogleCodeExporter commented 8 years ago 
The help text for the 'sync-c', 'sync-s' and 'sync-j' attributes have been 
updated.

Change uploaded to - 
https://gerrit-review.googlesource.com/#/c/58630/

Original comment by ray.sus...@gmail.com on 24 Jul 2014 at 11:11

GoogleCodeExporter commented 8 years ago 
Thanks :)

When should I expect this in the 'repo' distribution?

Original comment by avec...@motorola.com on 30 Jul 2014 at 2:10