From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] patches from 9front
Date: Tue, 9 Feb 2021 23:24:02 -0800 [thread overview]
Message-ID: <CAJSxfm+9F5yEwnzeijNFwq7yX-0oWqPK2vVo+fEm+GnS25ESww@mail.gmail.com> (raw)
In-Reply-To: <CAHwi9bzVbVYatRkbDPzkaAhy5AF7RXEu_PbyEkLGp+pTfpRUOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
no slight to the inventor of dp9ik, but has it been verified?
On Tue, Feb 9, 2021 at 7:48 PM Eli Cohen <echoline@gmail.com> wrote:
> On Tue, Feb 9, 2021 at 7:39 PM Lucio De Re <lucio.dere@gmail.com> wrote:
> >
> > On 2/10/21, Eli Cohen <echoline@gmail.com> wrote:
> > > I noticed the patches from 9front to 9legacy are not well-maintained.
> I'm
> > > trying to figure out if this would be an appreciated exercise from
> someone
> > > (me) who doesn't know all that much and would learn from doing it, and
> if
> > > so, what are priorities for things to port back as patches for 9legacy
> > >
> > In short: it's a bitch!
> >
> > I'm sure David will appreciate all the help he can get, but the code
> > divergences will not be easy to tame.
> >
> > I don't like Git, but I also don't think the Plan 9 "dump" is adequate
> > to the task of tracking "branches" as would apply in this complex
> > case.
> >
> > Perhaps I can recommend isolating bug fixes as distinct from adding
> > features, but where does one draw the line?
>
> I'm not even sure where or how to start. dp9ik seems important if
> 9legacy doesn't already have something similar. that's probably both a
> bug fix and feature... and quite a task! but I would be interested in
> porting patches back to learn more
>
> >
> > Best of luck, if you intend to proceed.
> >
> > Lucio.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc82939f1fda0e479-M4857c66d4e13e2d25ae337e0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3184 bytes --]
next prev parent reply other threads:[~2021-02-10 7:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 3:27 Eli Cohen
2021-02-10 3:37 ` Lucio De Re
2021-02-10 3:47 ` Eli Cohen
2021-02-10 4:14 ` Lucio De Re
2021-02-10 7:24 ` Skip Tavakkolian [this message]
2021-02-10 16:15 ` ori
2021-02-10 21:50 ` Eli Cohen
2021-02-10 22:00 ` ori
2021-02-10 22:26 ` David du Colombier
2021-02-11 5:49 ` ori
2021-02-11 7:24 ` Lucio De Re
2021-02-11 8:57 ` Jens Staal
2021-02-11 10:31 ` hiro
2021-02-11 11:57 ` Lucio De Re
2021-02-11 13:07 ` hiro
2021-02-11 17:41 ` pouya+lists.9fans
2021-02-11 8:40 ` David du Colombier
2021-02-12 1:21 ` ori
2021-02-12 2:55 ` Skip Tavakkolian
2021-02-12 17:42 ` ori
2021-02-12 17:48 ` sirjofri
2021-02-12 18:09 ` ori
2021-02-12 20:46 ` Lucio De Re
2021-02-12 23:54 ` Anthony Martin
2021-02-13 13:34 ` hiro
2021-02-13 14:05 ` Lucio De Re
2021-02-13 15:30 ` hiro
2021-02-22 18:44 ` David du Colombier
2021-02-23 4:45 ` ori
2021-03-19 14:41 ` Eli Cohen
2021-03-21 0:01 ` kokamoto
2021-03-21 8:33 ` David du Colombier
2021-03-21 9:46 ` hiro
2021-03-21 11:07 ` David du Colombier
2021-03-21 14:38 ` David du Colombier
2021-03-21 13:02 ` Ethan Gardener
2021-02-12 16:39 ` ori
2021-02-10 13:49 ` Steve Simon
2021-02-12 11:09 ` [9fans] 9pi provenance Richard Miller
2021-02-12 11:56 ` pouya+lists.9fans
2021-02-13 14:42 ` David du Colombier
2021-02-13 14:47 ` Richard Miller
2021-02-13 14:53 ` David du Colombier
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=CAJSxfm+9F5yEwnzeijNFwq7yX-0oWqPK2vVo+fEm+GnS25ESww@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/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).