Affected Version:
% repo --version
repo version v1.12.32
(from https://gerrit.googlesource.com/git-repo)
repo launcher version 1.22
(from /scratch/mhamilt/repos_test/google_repo/bin/repo)
git version 2.6.1
Python 2.7.4 (default, Aug 26 2013, 10:48:13)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)]
Environment:
Linux cee-build011 2.6.32-431.29.2.el6.x86_64 #1 SMP Sun Jul 27 15:55:46 EDT
2014 x86_64 x86_64 x86_64 GNU/Linux
What steps will reproduce the problem?
1. vi .repo/manifests/something.xml
2. repo status
3. repo init -m something.xml ...
What is the expected output? What do you see instead?
I expected the repo status output to show that I had modified the manifest
file. Instead it says 'working directory clean.' The repo init command proceeds
to update the working directory with the changes made to the manifest file.
Since it's using the file I think it should tell the developer that it is
modified.
Please provide any additional information below.
We are evaluating repo for use with our git repositories. We have set up a
number of different manifests for various groupings of code, and I wondered if
the developers could change the manifest on the fly and have it be used.
Clearly they can, and it's probably a good thing, but I think that repo status
should at least remind them that they did so.
Original issue reported on code.google.com by mham...@sandia.gov on 19 Nov 2015 at 9:46
Original issue reported on code.google.com by
mham...@sandia.govon 19 Nov 2015 at 9:46