From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: pipr-0.0.14
Date: Wed, 09 Sep 2020 01:32:56 +0200 [thread overview]
Message-ID: <20200908233256.Otc_ENo4SazYA1zkS5rhFaXwO8Fb9LaCbFoAhsGcemg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24769@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/24769#issuecomment-689189685
Comment:
On 2020-09-08 16:27:24-0700, Will Eccles <notifications@github.com> wrote:
> >
> > On 2020-09-08 13:40:46-0700, Will Eccles ***@***.***> wrote: Pipr
> > is a utility for interactively writing and previewing shell
> > pipelines. I will be maintaining the package.
> > Please learn the tool (Git and GitHub) instead of closing and re-opening.
>
> Git was very broken. The extra commit that it added to my branch
> (despite not being in the branch before) was unavailable for
> rebasing.
May I guess? It's a merge commit ;) or the commit available upstream.
Then Git is definitely not broken.
Why don't you try to finish the rebasing and check the result first ;)
> The rebase command refused to show the commit for me to
> delete it and I was unable to change anything about the commit. It
> was far easier to re-fork the repository than spend hours reading up
> on ancient git questions on SO.
next prev parent reply other threads:[~2020-09-08 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 20:40 [PR PATCH] " willeccles
2020-09-08 23:21 ` sgn
2020-09-08 23:27 ` willeccles
2020-09-08 23:32 ` sgn [this message]
2020-09-08 23:58 ` willeccles
2020-10-06 13:05 ` [PR PATCH] [Closed]: " willeccles
-- strict thread matches above, loose matches on Subject: below --
2020-09-08 17:34 [PR PATCH] " willeccles
2020-09-08 20:17 ` willeccles
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=20200908233256.Otc_ENo4SazYA1zkS5rhFaXwO8Fb9LaCbFoAhsGcemg@z \
--to=sgn@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).