Github messages for voidlinux
 help / color / mirror / Atom feed
From: littlewing7 <littlewing7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libtickit and libvterm update  
Date: Thu, 20 Apr 2023 12:17:59 +0200	[thread overview]
Message-ID: <20230420101759.bmBe4fZsP2qz5mbw9T82aczYC0cXHPMVQReFt1zuyuM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43532@inbox.vuxu.org>

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

New comment by littlewing7 on void-packages repository

https://github.com/void-linux/void-packages/pull/43532#issuecomment-1516080008

Comment:
hi, 

I'm new on this tasks I apologize,  I misunderstood the contributing guide.

I'm not expert in git use so  can you give me more help on how to correctly delete the merge commit or better redo the PR from scratch. 

can you please explain in simple way the correct command sequence for the PR, ex.:
is better to create a new branch for each one of the templates update? 
after I create the new branch locally and tested for example (./xbps-src pkg libtickit successful ),  PR must be requested using GITHUB web interface or there is a way to done this via command line directly from my local git repository?

can you kindly provide me a little list of steps to successfully complete this task? 

Many thanks for your help 

Max
 

  parent reply	other threads:[~2023-04-20 10:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 22:05 [PR PATCH] " littlewing7
2023-04-19 22:09 ` [PR PATCH] [Updated] " littlewing7
2023-04-19 22:14 ` mhmdanas
2023-04-19 22:15 ` mhmdanas
2023-04-20  6:40 ` [PR PATCH] [Updated] " littlewing7
2023-04-20 10:17 ` littlewing7 [this message]
2023-04-20 11:59 ` abenson
2023-04-20 12:04 ` abenson
2023-04-20 12:06 ` abenson
2023-04-20 12:07 ` abenson
2023-04-20 13:51 ` littlewing7
2023-04-26 13:59 ` littlewing7
2023-04-26 15:26 ` abenson
2023-04-26 20:23 ` [PR REVIEW] " mhmdanas
2023-04-26 20:23 ` mhmdanas
2023-04-26 20:23 ` mhmdanas
2023-04-26 22:04 ` littlewing7
2023-04-27 11:36 ` abenson
2023-04-27 11:39 ` littlewing7
2023-04-27 20:32 ` mhmdanas
2023-04-28  7:09 ` littlewing7
2023-04-28  7:10 ` littlewing7
2023-04-28  8:43 ` littlewing7
2023-05-03 16:44 ` [PR PATCH] [Updated] " littlewing7
2023-05-03 16:55 ` littlewing7
2023-05-03 17:03 ` [PR PATCH] [Updated] libtickit update littlewing7
2023-05-03 17:05 ` littlewing7
2023-05-03 17:16 ` littlewing7
2023-05-03 17:19 ` littlewing7
2023-05-03 17:27 ` [PR PATCH] [Closed]: " 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=20230420101759.bmBe4fZsP2qz5mbw9T82aczYC0cXHPMVQReFt1zuyuM@z \
    --to=littlewing7@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).