~ke

Recent activity

Re: [PATCH swayr 0/1] Add wifi module 1 year, 6 months ago

From Karl Eklund to ~tsdh/public-inbox

Karl Eklund <localpart@gmail.com> writes:

> I deleted my fork and recreated it, but the git clone problem persisted.
> So I cloned it to Github... Here is a new "git request-pull" patch, one
> commit, rebased on latest upstream.

Please ignore the previous message. It is not the right commit. It only
contained my first commit. I did something wrong when rebasing.

Here is the proper one. The branch is called nmcli now.

Sorry.

The following changes since commit 0ea753f4e14b1a3174a8fcee46a5447b390b0039:
[message trimmed]

Re: [PATCH swayr 0/1] Add wifi module 1 year, 6 months ago

From Karl Eklund to ~tsdh/public-inbox

Karl Eklund <localpart@gmail.com> writes:

> Tassilo Horn <tsdh@gnu.org> writes:
>
>> Tassilo Horn <tsdh@gnu.org> writes:
>>
>> I've asked on #srht on libera.chat.  There is or was some issue where
>> cloning a repo using the "Clone repo to your account" button resulted in
>> a broken repo with exactly the above problem.  When did you clone the
>> repo to your account?
>>
>> Anyway, I suggest you simply rebase your commits on the wifi branch and
>> squash them into a single commit and then send that as a new patch to
>> this list again.
[message trimmed]

Re: [PATCH swayr 0/1] Add wifi module 1 year, 6 months ago

From Karl Eklund to ~tsdh/public-inbox

Tassilo Horn <tsdh@gnu.org> writes:

>
> Whatever you prefer.  When I should merge from you, it's best you send
> the output of
>
>   $ git request-pull -p \
>       origin/master \
>       https://my.repo.com/my-fork \
>       wifi
>
> where origin is the name of the swayr upstream remote and the URL is the
> one of your fork.
[message trimmed]

Re: [PATCH swayr 0/1] Add wifi module 1 year, 6 months ago

From Karl Eklund to ~tsdh/public-inbox

Tassilo Horn <tsdh@gnu.org> writes:

> ~ke <ke@git.sr.ht> writes:
>
> Hi Karl,
>
>> Add a wifi module which can display wifi network name and signal
>> strength.
>
> Thank you, that's a highly welcome addition.
>
>> It gathers this information by running nmcli.
>
> Hm, that's ok but in this case, I'd rather name the module nmcli instead