From 1fc994f588dd9ef2ef8395e57e2492a6b4d730eb Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Sun, 16 Jan 2022 16:52:43 -0300 Subject: git mv locale/ po/ --- .../_tils/2020-11-12-git-bisect-automation.po | 53 ---------------------- 1 file changed, 53 deletions(-) delete mode 100644 locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po (limited to 'locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po') diff --git a/locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po b/locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po deleted file mode 100644 index 09ec261..0000000 --- a/locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po +++ /dev/null @@ -1,53 +0,0 @@ -# -msgid "" -msgstr "" - -msgid "title: Git bisect automation" -msgstr "" - -msgid "layout: post" -msgstr "" - -msgid "lang: en" -msgstr "" - -msgid "ref: git-bisect-automation" -msgstr "" - -msgid "" -"It is good to have an standardized way to run builds and tests on the " -"repository of a project, so that you can find when a bug was introduced by " -"using `git bisect run`." -msgstr "" - -msgid "" -"I've already been in the situation when a bug was introduced and I didn't " -"know how it even was occurring, and running Git bisect over hundreds of " -"commits to pinpoint the failing commit was very empowering:" -msgstr "" - -msgid "" -"$ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46\n" -"$ git bisect start HEAD $GOOD_COMMIT_SHA\n" -"$ git bisect run sn -c './build.sh && ./run-failing-case.sh'\n" -msgstr "" - -msgid "" -"Git will than do a binary search between the commits, and run the commands " -"you provide it with to find the failing commit." -msgstr "" - -msgid "" -"Instead of being afraid of doing a bisect, you should instead leverage it, " -"and make Git help you dig through the history of the repository to find the " -"bad code." -msgstr "" - -msgid "date: 2020-11-12 2" -msgstr "" - -msgid "eu_categories: git" -msgstr "" - -#~ msgid "date: 2020-11-12" -#~ msgstr "" -- cgit v1.2.3