The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.
Zen

Translation

You can prevent yourself fromTo avoid accidentally pushing unsigned commits to Savannah by using the pre-push Git hook located at @file{etc/git/pre-push}:or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.
type: Plain text
To avoid accidentally pushing unsigned or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.
152/1520 · 152

This translation is currently locked.

English Turkish Actions
digest-algo sha512
özet-algo sha512
Maintainers ultimately decide whether to grant you commit access, usually following your referrals' recommendation.
Bakımcılar, genellikle önerilerinizi dinleyerek, size erişim izni verip vermemeye karar verirler.
OpenPGP, signed commits
OpenPGP, imzalanmış taahhütler
If and once you've been given access, please send a message to @email{guix-devel@@gnu.org} to say so, again signed with the OpenPGP key you will use to sign commits (do that before pushing your first commit). That way, everyone can notice and ensure you control that OpenPGP key.
 
Important
Önemli
Before you can push for the first time, maintainers must:
İlk kez push yapman önce, maintainerlar şunları yapmalıdır:
add your OpenPGP key to the @code{keyring} branch;
OpenPGP anahtarınızı @code{keyring} brachına ekleyin;
add your OpenPGP fingerprint to the @file{.guix-authorizations} file of the branch(es) you will commit to.
 
Make sure to read the rest of this section and... profit!
Bu bölümün geri kalanını okuduğunuzdan emin olun ve... kazançlı çıkın!
Maintainers are happy to give commit access to people who have been contributing for some time and have a track record---don't be shy and don't underestimate your work!
Bakımcılar, bir süredir katkıda bulunan ve bir geçmişe sahip kişilere erişim vermekten mutluluk duyarlar --- utangaç olmayın ve işinizi küçümsemeyin!
However, note that the project is working towards a more automated patch review and merging system, which, as a consequence, may lead us to have fewer people with commit access to the main repository. Stay tuned!
 
All commits that are pushed to the central repository on Savannah must be signed with an OpenPGP key, and the public key should be uploaded to your user account on Savannah and to public key servers, such as @code{keys.openpgp.org}. To configure Git to automatically sign commits, run:
Savannah'daki depoya gönderilen tüm taahhütler bir OpenPGP anahtarıyla imzalanmalıdır ve ortak anahtar Savannah'daki kullanıcı hesabınıza ve @code{keys.openpgp.org} gibi ortak anahtar sunucularına yüklenmelidir. Git'i taahhütleri otomatik olarak imzalayacak şekilde yapılandırmak için şunu çalıştırın:
git config commit.gpgsign true
git config commit.gpgsign true
# Substitute the fingerprint of your public PGP key.
git config user.signingkey CABBA6EA1DC0FF33
# Genel PGP anahtarınızın parmak izini değiştirin.
git config user.signingkey CABBA6EA1DC0FF33
To check that commits are signed with correct key, use:
 
To avoid accidentally pushing unsigned or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.
@file{etc/git/pre-push} konumunda bulunan pre-push Git kancasını kullanarak imzasız taahhütleri yanlışlıkla Savannah'ya gönderilmesini önleyebilirsiniz:
Commit Policy
Sözleşme Politikası
If you get commit access, please make sure to follow the policy below (discussions of the policy can take place on @email{guix-devel@@gnu.org}).
Taahhüt erişimi alırsanız, lütfen aşağıdaki politikaya uyduğunuzdan emin olun (politika tartışmaları @email{guix-devel@@gnu.org} adresinde yapılabilir).
Ensure you're aware of how the changes should be handled (@pxref{Managing Patches and Branches}) prior to being pushed to the repository, especially for the @code{master} branch.
 
If you're committing and pushing your own changes, try and wait at least one week (two weeks for more significant changes) after you send them for review. After this, if no one else is available to review them and if you're confident about the changes, it's OK to commit.
 
When pushing a commit on behalf of somebody else, please add a @code{Signed-off-by} line at the end of the commit log message---e.g., with @command{git am --signoff}. This improves tracking of who did what.
 
When adding channel news entries (@pxref{Channels, Writing Channel News}), make sure they are well-formed by running the following command right before pushing:
 
make check-channel-news
kontrol-kanal-haber yapmak
Addressing Issues
Sorunları Ele Alma
Peer review (@pxref{Submitting Patches}) and tools such as @command{guix lint} (@pxref{Invoking guix lint}) and the test suite (@pxref{Running the Test Suite}) should catch issues before they are pushed. Yet, commits that ``break'' functionality might occasionally go through. When that happens, there are two priorities: mitigating the impact, and understanding what happened to reduce the chance of similar incidents in the future. The responsibility for both these things primarily lies with those involved, but like everything this is a group effort.
 
Some issues can directly affect all users---for instance because they make @command{guix pull} fail or break core functionality, because they break major packages (at build time or run time), or because they introduce known security vulnerabilities.
 
reverting commits
geri alma taahhütleri
The people involved in authoring, reviewing, and pushing such commit(s) should be at the forefront to mitigate their impact in a timely fashion: by pushing a followup commit to fix it (if possible), or by reverting it to leave time to come up with a proper fix, and by communicating with other developers about the problem.
 
If these persons are unavailable to address the issue in time, other committers are entitled to revert the commit(s), explaining in the commit log and on the mailing list what the problem was, with the goal of leaving time to the original committer, reviewer(s), and author(s) to propose a way forward.
 
Once the problem has been dealt with, it is the responsibility of those involved to make sure the situation is understood. If you are working to understand what happened, focus on gathering information and avoid assigning any blame. Do ask those involved to describe what happened, do not ask them to explain the situation---this would implicitly blame them, which is unhelpful. Accountability comes from a consensus about the problem, learning from it and improving processes so that it's less likely to reoccur.
 
Commit Revocation
İptal İşlemi Yap

Loading…

User avatar None

String updated in the repository

  1. guix
  2. documentation-manual
  3. Turkish
To avoid accidentally pushing unsigned or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.
@file{etc/git/pre-push} konumunda bulunan pre-push Git kancasını kullanarak imzasız taahhütleri yanlışlıkla Savannah'ya gönderilmesini önleyebilirsiniz:
12 months ago
User avatar None

Source string changed

  1. guix
  2. documentation-manual
  3. Turkish
You can prevent yourself fromTo avoid accidentally pushing unsigned commits to Savannah by using the pre-push Git hook located at @file{etc/git/pre-push}:or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.
12 months ago
Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English Turkish
No related strings found in the glossary.

String information

Source string description
type: Plain text
Source string location
guix-git/doc/contributing.texi:2677
String age
12 months ago
Last updated
10 months ago
Source string age
12 months ago
Translation file
po/doc/guix-manual.tr.po, string 707