You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by Andrew D. Stadler (Google) <stadler@android.com> on Fri May 22
16:32:51 PDT 2009
Source: JIRA REPO-34
The output of repo sync is entirely internal and quite repetitive:
$ repo sync
remote: Counting objects: 16, done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 11 (delta 6), reused 3 (delta 0)
Unpacking objects: 100% (11/11), done.
From git://android.git.kernel.org/tools/repo
2f968c9..498a0e8 master -> origin/master
2f968c9..498a0e8 stable -> origin/stable
* [new tag] v1.6.7.5 -> v1.6.7.5
From git://android.git.kernel.org/tools/repo
* [new tag] v1.6.7.4 -> v1.6.7.4
remote: Counting objects: 78, done
remote: Compressing objects: 100% (63/63)
Unpacking objects: 100% (63/63), done.
From ssh://android-git.corp.google.com:29418/platform/manifest
d2f06d9..d9584ca cupcake -> origin/cupcake
78ef62e..9d863ff donut -> origin/donut
22f7151..fc3614e donut-release -> origin/donut-release
* [new branch] eclair-release -> origin/eclair-release
8c6d287..c122554 master -> origin/master
9b08529..8d04dec master_gl -> origin/master_gl
remote: Counting objects: 2126, done
remote: Compressing objects: 100% (45/45)
Unpacking objects: 100% (45/45), done.
This kind of stuff isn't really interesting to the "average user" who just
wants latest files. Can you put it under a -v type option?
Second, the final step is not verbose enough:
Syncing work tree: 79% (120/151)
And this is exactly where the "average user" would like to see *more* output:
What files were updated on my machine?
Can you please change repo sync to be more like this:
$ repo sync
Updating repositories.... (maybe do a live % thing here?)
Syncing work tree:
updating: packages/apps/Calendar/myActivity.java
updating: packages/apps/Email/providers.xml
..etc...
$
Original issue reported on code.google.com by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
code-rev...@gtempaccount.com
on 24 Sep 2009 at 9:10The text was updated successfully, but these errors were encountered: