Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for emojisi (0.04 sec)

  1. docs/tr/docs/async.md

    Ancak *eşzamanlılık* ve *paralellik* arasındaki ayrıntılar oldukça farklıdır.
    
    
    Farkı görmek için burgerlerle ilgili aşağıdaki hikayeyi hayal edin:
    
    ### Eşzamanlı Burgerler
    
    <!-- Cinsiyetten bağımsız olan aşçı emojisi "🧑‍🍳" tarayıcılarda yeterince iyi görüntülenmiyor. Bu yüzden erken "👨‍🍳" ve kadın "👩‍🍳" aşçıları karışık bir şekilde kullanıcağım. -->
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Tue Aug 06 04:48:30 UTC 2024
    - 21.9K bytes
    - Viewed (0)
  2. docs/en/docs/management-tasks.md

    ## Edit PR Titles
    
    * Edit the PR title to start with an emoji from <a href="https://gitmoji.dev/" class="external-link" target="_blank">gitmoji</a>.
        * Use the emoji character, not the GitHub code. So, use `🐛` instead of `:bug:`. This is so that it shows up correctly outside of GitHub, for example in the release notes.
        * For translations use the `🌐` emoji ("globe with meridians").
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Fri Aug 16 21:56:33 UTC 2024
    - 14.2K bytes
    - Viewed (0)
  3. docs/ru/docs/async.md

    Но внутреннее устройство **конкурентности** и **параллелизма** довольно разное.
    
    Чтобы это понять, представьте такую картину:
    
    ### Конкурентные бургеры
    
    <!-- The gender neutral cook emoji "🧑‍🍳" does not render well in browsers. In the meantime, I'm using a mix of male "👨‍🍳" and female "👩‍🍳" cooks. -->
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Tue Aug 06 04:48:30 UTC 2024
    - 39.9K bytes
    - Viewed (0)
  4. docs/changelogs/changelog_2x.md

     *  **OkHttp now rejects request headers that contain invalid characters.** This
        includes potential security problems (newline characters) as well as simple
        non-ASCII characters (including international characters and emoji).
    
     *  **Call canceling is more reliable.**  We had a bug where a socket being
         connected wasn't being closed when the application used `Call.cancel()`.
    
    Registered: Fri Nov 01 11:42:11 UTC 2024
    - Last Modified: Sun Feb 06 02:19:09 UTC 2022
    - 26.6K bytes
    - Viewed (0)
Back to top