Github messages for voidlinux
 help / color / mirror / Atom feed
From: carvalhudo <carvalhudo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] CONTRIBUTING.md: removing duplicated word from file
Date: Thu, 05 Jan 2023 04:26:19 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41462@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 452 bytes --]

There is a new pull request by carvalhudo against master on the void-packages repository

https://github.com/carvalhudo/void-packages fix_typo_contrib_file
https://github.com/void-linux/void-packages/pull/41462

CONTRIBUTING.md: removing duplicated word from file
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**: **YES**

A patch file from https://github.com/void-linux/void-packages/pull/41462.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix_typo_contrib_file-41462.patch --]
[-- Type: text/x-diff, Size: 1131 bytes --]

From e40b6a930319e4dff33cf4f2643930357e62a6c5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20L=2E=20C=2E=20Moreira?= <alcm99@gmail.com>
Date: Thu, 5 Jan 2023 00:13:23 -0300
Subject: [PATCH] CONTRIBUTING.md: removing duplicated word

removing duplicated 'the' from the section 'Creating, updating, and
modifying packages in Void by yourself'
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ab24ede1f341..529dddf20a9c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -56,7 +56,7 @@ This automatically sets up the `upstream` remote, so `git pull --rebase upstream
 
 Using the GitHub web editor for making changes is strongly discouraged, because you will need to clone the repo anyways to edit and test your changes.
 
-using the the `master` branch of your fork for contributing is also strongly discouraged.
+using the `master` branch of your fork for contributing is also strongly discouraged.
 It can cause many issues with updating your pull request (also called a PR), and having multiple PRs open at once.
 To create a new branch:
 

             reply	other threads:[~2023-01-05  3:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  3:26 carvalhudo [this message]
2023-01-07 10:56 ` CONTRIBUTING.md: removing duplicated word Chocimier
2023-01-07 14:45 ` [PR PATCH] [Updated] " carvalhudo
2023-01-07 14:45 ` carvalhudo
2023-01-07 17:51 ` [PR PATCH] [Merged]: " abenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41462@inbox.vuxu.org \
    --to=carvalhudo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).