Skip to content

Passing pomerge locally. #1046

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 6, 2019
Merged

Passing pomerge locally. #1046

merged 1 commit into from
Dec 6, 2019

Conversation

JulienPalard
Copy link
Member

I mean:

pomerge --from-files *.po */*.po
pomerge --no-overwrite --to-files *.po */*.po
powrap -m

@JulienPalard JulienPalard merged commit 7923a1f into python:3.8 Dec 6, 2019
@deronnax
Copy link
Collaborator

deronnax commented Dec 7, 2019

Avec ça tu propages les traduction de fichiers .po déjà renseignés dans des .po qui contiennent les mêmes string mais non traduites, c'est ça ?

@JulienPalard
Copy link
Member Author

Avec ça tu propages les traduction de fichiers .po déjà renseignés dans des .po qui contiennent les mêmes string mais non traduites, c'est ça ?

Exact :] Avec le même outil, mais entrecoupé de "git checkout" je propage d'une branche a l'autre, c.f. les backports d'hier ou avant hier sur les branches 3.7, 3.6, et 2.7.

@JulienPalard JulienPalard deleted the pomerge branch June 7, 2021 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants