From: hiro <firstname.lastname@example.org>
Subject: Re: [9front] [PATCH] Permissions for child boards in /srv
Date: Wed, 29 Jun 2022 19:12:11 +0200 [thread overview]
Message-ID: <CAFSF3XOtJhvxZNGN-Wyhf+B=gJupfkawy1BM37ubvi+gFkpE2A@mail.gmail.com> (raw)
you guys know there are also branches?
On 6/29/22, email@example.com <firstname.lastname@example.org> wrote:
> Quoth Jacob Moody <email@example.com>:
>> On 6/29/22 10:35, firstname.lastname@example.org wrote:
>> > but thats not just what this patch does.
>> > it changes all kinds of stuff.
>> > i'd suggest we revert everything at this point.
>> It's disheartening you feel this way. I will
>> begin the process of reverting all of my commits
>> from the past month or so.
> The ideas are good, but we need to get them right
> before we push them to other people's computers.
> I use whatever's committed to actually write code
> for work :)
next prev parent reply other threads:[~2022-06-29 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:34 Jacob Moody
2022-06-25 3:49 ` Jacob Moody
2022-06-29 14:53 ` Jacob Moody
2022-06-29 16:35 ` cinap_lenrek
2022-06-29 16:42 ` Jacob Moody
2022-06-29 16:46 ` ori
2022-06-29 17:12 ` hiro [this message]
2022-06-29 17:20 ` cinap_lenrek
2022-06-29 17:50 ` Jacob Moody
2022-07-02 21:25 ` ori
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).