git mv locale/ po/

1 files changed, 164 insertions, 0 deletions

diff --git a/po/eo/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po b/po/eo/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po
new file mode 100644
index 0000000..4b43e70
--- /dev/null
+++ b/po/eo/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po
@@ -0,0 +1,164 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"It might be news to you, as it was to me, that \"pull requests\" that you "
+"can create on a Git hosting provider's web UI[^pr-webui] like "
+"GitLab/Bitbucket/GitHub actually comes from Git itself: `git request-pull`."
+msgstr ""
+
+msgid ""
+"[^pr-webui]: And maybe even using the Git hosting provider's API from the "
+"command line!"
+msgstr ""
+
+msgid ""
+"At the very core, they accomplish the same thing: both the original and the "
+"web UI ones are ways for you to request the project maintainers to pull in "
+"your changes from your fork. It's like saying: \"hi there, I did some "
+"changes on my clone of the repository, what do you think about bringing "
+"those in?\"."
+msgstr ""
+
+msgid ""
+"The only difference is that you're working with only Git itself, so you're "
+"not tied to any Git hosting provider: you can send pull requests across them"
+" transparently! You could even use your own "
+"[cgit](https://git.zx2c4.com/cgit/) installation. No need to be locked in by"
+" any of them, putting the \"D\" back in \"DVCS\": it's a **distributed** "
+"version control system."
+msgstr ""
+
+msgid "`git request-pull` introduction"
+msgstr ""
+
+msgid "Here's the raw output of a `git request-pull`:"
+msgstr ""
+
+msgid ""
+"That very first line is saying: \"create me a pull request with only a "
+"single commit, defined by `HEAD`, and use the URL defined by `public-"
+"origin`\"."
+msgstr ""
+
+msgid ""
+"Here's a pitfall: you may try using your `origin` remote at first where I "
+"put `public-origin`, but that is many times pointing to something like "
+"`git@example.com`, or `git.example.com:repo.git` (check that with `git "
+"remote -v | grep origin`). On both cases those are addresses available for "
+"interaction via SSH, and it would be better if your pull requests used an "
+"address ready for public consumption."
+msgstr ""
+
+msgid ""
+"A simple solution for that is for you to add the `public-origin` alias as "
+"the HTTPS alternative to the SSH version:"
+msgstr ""
+
+msgid "Every Git hosting provider exposes repositories via HTTPS."
+msgstr ""
+
+msgid "Experiment it yourself, and get acquainted with the CLI."
+msgstr ""
+
+msgid "Delivering decentralized pull requests"
+msgstr ""
+
+msgid ""
+"Now that you can create the content of a pull request, you can just [deliver"
+" it][cli-email] to the interested parties email:"
+msgstr ""
+
+msgid ""
+"[cli-email]: {% link _tils/2020-09-04-send-emails-using-the-command-line-"
+"for-fun-and-profit.md %}"
+msgstr ""
+
+msgid "Conclusion"
+msgstr ""
+
+msgid ""
+"In practice, I've never used or seen anyone use pull requests this way: "
+"everybody is just [sending patches via "
+"email](https://drewdevault.com/2018/07/23/Git-is-already-distributed.html)."
+msgstr ""
+
+msgid ""
+"If you stop to think about this model, the problem of \"Git hosting "
+"providers becoming too centralized\" is a non-issue, and \"Git federation\" "
+"proposals are a less attractive as they may sound initially."
+msgstr ""
+
+msgid ""
+"Using Git this way is not scary or so weird as the first impression may "
+"suggest. It is actually how Git was designed to be used."
+msgstr ""
+
+msgid "Check `git help request-pull` for more info."
+msgstr ""
+
+msgid ""
+"$ git request-pull HEAD public-origin\n"
+"The following changes since commit 302c9f2f035c0360acd4e13142428c100a10d43f:\n"
+"\n"
+"  db post: Add link to email exchange (2020-09-03 21:23:55 -0300)\n"
+"\n"
+"are available in the Git repository at:\n"
+"\n"
+"  https://euandreh.xyz/website.git/\n"
+"\n"
+"for you to fetch changes up to 524c646cdac4153e54f2163e280176adbc4873fa:\n"
+"\n"
+"  db post: better pinpoint sqlite unsuitability (2020-09-03 22:08:56 -0300)\n"
+"\n"
+"----------------------------------------------------------------\n"
+"EuAndreh (1):\n"
+"      db post: better pinpoint sqlite unsuitability\n"
+"\n"
+" _posts/2020-08-31-the-database-i-wish-i-had.md | 12 ++++++------\n"
+" 1 file changed, 6 insertions(+), 6 deletions(-)\n"
+msgstr ""
+
+msgid "$ git remote add public-origin https://example.com/user/repo\n"
+msgstr ""
+
+msgid ""
+"# send a PR with your last commit to the author's email\n"
+"git request-pull HEAD public-origin | mail author@example.com -s \"PR: Add thing to repo\"\n"
+"\n"
+"# send a PR with your last 5 commits to the project's mailing\n"
+"# list, including the patch\n"
+"git request-pull HEAD~5 public-origin -p | \\\n"
+"  mail list@example.com -s \"PR: Add another thing to repo\"\n"
+"\n"
+"# send every commit that is new in \"other-branch\"\n"
+"git request-pull master public-origin other-branch | \\\n"
+"  mail list@example.com -s 'PR: All commits from my \"other-brach\"'\n"
+msgstr ""
+
+msgid "title: Pull requests with Git, the old school way"
+msgstr ""
+
+msgid "date: 2020-09-05"
+msgstr ""
+
+msgid "layout: post"
+msgstr ""
+
+msgid "lang: en"
+msgstr ""
+
+msgid "ref: pull-requests-with-git-the-old-school-way"
+msgstr ""
+
+msgid "eu_categories: git"
+msgstr ""
+
+#~ msgid ""
+#~ "title: Pull requests with Git, the old school way\n"
+#~ "date: 2020-09-05\n"
+#~ "layout: post\n"
+#~ "lang: en\n"
+#~ "ref: pull-requests-with-git-the-old-school-way"
+#~ msgstr ""