[configuration] define how l10n-merge should work

RESOLVED FIXED

Status

RESOLVED FIXED
2 years ago
a year ago

People

(Reporter: Pike, Assigned: Pike)

Tracking

Details

(Assignee)

Description

2 years ago
In the new configuration world, is there a well defined canonical behavior on how l10n-merge should work?

In particular, for

[[paths]]
    reference = "browser/branding/official/locales/en-US/**"
    l10n = "{l}browser/branding/official/**"

we might not find out what's {l} at the time when we hand things down, or that that's the intended behavior.

Needs more thought and comments.
(Assignee)

Comment 1

a year ago
This was solved in bug 1368025.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.