Hi everybody,
The main Git repository has just been tagged with v2.27.0-rc0, which is starting the cycle of release candidates. In a few weeks the final 2.27.0 will be released. To keep up with this cycle, I updated our english source files with the changes introduced in the documentation.
Some of the texts which were already translated will need to be reviewed and amended. Please do it in priority, so that we can update the pages on git-scm at the time the version is ready for download.
Moreover, I'm starting a project to publish the translated manpages as a package for Debian Linux . Hopefully, this will be followed by the availability in all Debian-based Linux distributions. If some of you are interested in joining the effort to publish these manpages elsewhere, please contact me.
Best regards,
Jean-Noël
View contributor agreement
Contribution to this translation requires you to agree with a contributor agreement.
Please sign in to see the alerts.
| Project website | https://git-scm.com | |
|---|---|---|
| Translation process |
|
|
| Translation license | GNU General Public License v2.0 only | |
| Contributor agreement | View | |
| Repository |
https://github.com/jnavila/git-manpages-l10n
|
|
| Repository branch | master | |
| Last remote commit |
fixup for addenda and french addendum
3cb7668
 jnavila authored 2 days ago |
|
| Repository containing Weblate translations |
https://hosted.weblate.org/git/git-manpages/translations/
|
|
| Filemask | po/documentation.*.po |
|
| Number of strings | 196,422 | |
| Number of words | 3,769,733 | |
| Number of characters | 24,183,086 | |
| Number of languages | 19 | |
| Number of source strings | 10,338 | |
| Number of source words | 198,407 | |
| Number of source characters | 1,272,794 | |
wtuemura
Limit the commits output to ones with log message that matches the specified pattern (regular expression). With more than one `--grep=<pattern>`, commits whose message matches any of the given patterns are chosen (but see `--all-match`).
Limite a saída dos commits para aqueles com mensagem de registro log que coincida com padrão determinado (expressão regular). Com mais de um `--grep=<pattern>`, faça o commit daqueles cuja mensagem coincida com qualquer um dos padrões determinado (mas vejaporém consulte `--all-match`).
Override the commit author. Specify an explicit author using the standard `A U Thor <author@example.com>` format. Otherwise <author> is assumed to be a pattern and is used to search for an existing commit by that author (i.e. rev-list --all -i --author=<author>); the commit author is then copied from the first such commit found.
Sobrescrevera o commit do autor. Determina o autor de forma explicita ustilizando o formato padrão `A U Thor <author@example.com>`. Caso contrário assume-se <author> como padrão e será utilizado na pesquisa de um commit existente feito por este autor (ou seja, rev-list --all -i --author=<author>); o commit do autor é então copiado do primeiro commit que for encontrado.
Using `--recurse-submodules` will update the content of all active submodules according to the commit recorded in the superproject. If nothing (or `--no-recurse-submodules`) is used, submodules working trees will not be updated. Just like linkgit:git-submodule[1], this will detach `HEAD` of the submodules.
O uso de `--recurse-submodules` atualizará o conteúdo de todos os submódulos inicializadativos de acordo com o commit registrado no superprojeto. Se nada (ou `--no-recurse-submodules`) for usado, os submódulos das árvores de trabalho dos submódulos não serão atualizadaos. Assim como em linkgit:git-submodule[1], isso faz com que `HEAD` seja desanexado do submódulo.
If `<pathspec>` names an active submodule and the restore location includes the working tree, the submodule will only be updated if this option is given, in which case its working tree will be restored to the commit recorded in the superproject, and any local modifications overwritten. If nothing (or `--no-recurse-submodules`) is used, submodules working trees will not be updated. Just like linkgit:git-checkout[1], this will detach `HEAD` of the submodule.
Caso o`<pathspec>` dê nome para um submódulo ativo e o ponto de restauração inclua a árvore de trabalho, o submódulo apenas será atualizado caso essa informação seja utilizada, no caso, a sua árvore de trabalho será restaurado ao commit registrado no superprojeto e quaisquer alterações locais será substituida. Caso nenhum (ou `--no-recurse-submodules`) seja utilizado, os submódulos nas árvores de trabalho não serão atualizados. Assim como linkgit:git-checkout[1], isso irá desanexar o `HEAD` do submódulo.
If `<pathspec>` names an active submodule and the restore location includes the working tree, the submodule will only be updated if this option is given, in which case its working tree will be restored to the commit recorded in the superproject, and any local modifications overwritten. If nothing (or `--no-recurse-submodules`) is used, submodules working trees will not be updated. Just like linkgit:git-checkout[1], this will detach `HEAD` of the submodule.
Using --recurse-submodules will update the content of all active submodules according to the commit recorded in the superproject by calling read-tree recursively, also setting the submodules' HEAD to be detached at that commit.
BusquCapture tuodos os reamotamentes remotos.