grit is now part of Chromium's repository and no longer pulled through DEPS

[Nico Weber]

Hi,

grit is now checked in to Chromium's repository. If you want to change grit, you now need a Chromium checkout to do so – on the flip side, no DEPS rolls need to happen after a grit change any more. Since all grit developers are Chromium developers in practice, this seemed like a good change. (The tracking bug was http://crbug.com/553682)

If you are using grit and don't want to check out all of Chromium, https://chromium.googlesource.com/chromium/src/tools/grit/ is a read-only mirror of the grit code in Chromium's repository. So you could pull from there.

Nico

[Pavel Sergeev]

Where grit issues should be reported to: Chromium tracker or https://code.google.com/p/grit-i18n/issues?

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

[Nico Weber]

On Thu, Nov 12, 2015 at 7:54 PM, Pavel Sergeev <dzh...@chromium.org> wrote:

Where grit issues should be reported to: Chromium tracker or https://code.google.com/p/grit-i18n/issues?

The grit-i18n one is on codesite which is going away soon, so I'd say on the Chromium tracker.

[Jason Robbins]

We could migrate your grit-i18n issues to bugs.chromium.org (monorail) if you like.

Thanks,

jason!

On Thu, Nov 12, 2015 at 7:54 PM, Pavel Sergeev <dzh...@chromium.org> wrote:

---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Nico Weber]

Since the code is now in the Chromium repo, having a separate bug tracker for that subdirectory seems a bit weird.

(And realistically, if someone wants to have some bug in grit fixed, they'll likely have to fix it themselves anyways.)

[John Abd-El-Malek]

Awesome, we should do more of this :)

--

[Nick Carter]

Somehow, after trying to sync this morning, 'origin/master' on my main chromium checkout is now tracking grit-i18n.googlecode.com instead of the chromium mainline (my local branches are intact). Mentioning it here in case someone else hits it; seems not worth debugging unless widespread.

Steps that may have triggered this:

 - my initial 'git pull' (which would have pulled in new grit) failed the merge step because of a locked file in tools/grit.

 - after resetting, I did a 'gclient sync -f -D' on top of the old branch (with the old style grit).

 - 'git pull' failed again (with the locked file), so I moved tools/grit aside (to the parent of my src/ dir).

[Ojan Vafai]

Yes please! Let's enforce good isolation more through include-guards and less through different repos wherever we can!

[WC Leung]

Dear all,

    Today I want to commit my changes, and I've seen the following:

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

        new file:   tools/grit/LICENSE
        new file:   tools/grit/codereview.settings

    Is it okay to delete that two files?

Regards,
WC Leung.

[Nico Weber]

These two files were deleted here:

https://chromium.googlesource.com/chromium/src/+/3944083d60cd9eb76dc61d2a9860f8e6e00ba056

https://chromium.googlesource.com/chromium/src/+/58853167e39b75d47e212c465235ed0040227dcf

How are you trying to commit? How did you check out grit? Do you have a normal Chromium checkout?

--

[WC Leung]

Thanks! Apparently my recent "git rebase-update" and "gclient sync" failed to delete that two files, which is completely normal because we've moved grit from one repository to another. So I am content with manually deleting that two files myself.

BTW, what I refer as commit is a local commit, which will be uploaded by "git cl upload". No worries!

Regards,
WC Leung.