same here, I've got stuck on at a random revision #, couldn't get it move forward with 'gclient sync'

On Thu, Jun 28, 2012 at 9:25 AM, Satoru Takabayashi <satorux <at> chromium.org> wrote:

http://code.google.com/p/chromium/issues/detail?id=134858

I also got into the same weird state.

On Thu, Jun 28, 2012 at 9:20 AM, James Cook <jamescook <at> chromium.org> wrote:

I got into a confusing state this morning where repeated gclient sync commands did not update my working copy.  I was doing this:

$ git checkout master

$ gclient sync --jobs=16

$ git log -3

It would not advance master past svn revision 144718.  To work around this I did the following:

$ git checkout master

$ git fetch

$ git rebase origin/master

$ gclient sync --jobs=16

The "git fetch" step didn't used to be necessary.  Do I need to do this now?  The documentation for NewGitWorkflow implies to me that "git fetch" is optional: http://code.google.com/p/chromium/wiki/UsingNewGit#Updating_the_code

Do the docs need to be updated?

Thanks,

James

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev