On Thu, 22 Feb 2024 at 00:08, tison wrote:
>
> It's currently a brand new branch. You can check it in the repo.
OK, great. It seems I was misled by the summary page, which says:
"This branch is 5 commits ahead of, 34 commits behind master."
To me, that definitely implies a relationship. Very
It's currently a brand new branch. You can check it in the repo.
Best,
tison.
sebb 于2024年2月22日 周四01:11写道：
> On Wed, 21 Feb 2024 at 09:25, tison wrote:
> >
> > Hi sebb,
> >
> > Your comments sound like back to the switching default branch solution (a
> > new branch with history only adding the
On Wed, 21 Feb 2024 at 09:25, tison wrote:
>
> Hi sebb,
>
> Your comments sound like back to the switching default branch solution (a
> new branch with history only adding the README becomes the default).
I am saying that if the 3 branch solution is adopted the docusaurus
branch should be
> On Feb 20, 2024, at 11:02 PM, Lukasz Lenart wrote:
>
> wt., 20 lut 2024 o 19:19 Craig Russell napisał(a):
>> So I thought there was more content which would require transferring IP
>> rights. But if it's just a trivial bit of a web page, no issues.
>
> The only issue with the page right
Thanks for answering
> On Feb 21, 2024, at 12:34 AM, sebb wrote:
>
> The mailing lists already exist.
>
> However the podling status files are out of date so clutch cannot find
> the information it needs.
These status files consist of both an xml and a later yml file.
I’d like to start a
Hi sebb,
Your comments sound like back to the switching default branch solution (a
new branch with history only adding the README becomes the default).
Or you prefer other ways to the same repo direction.
Also is it possible we go back to the COMDEV dedicated thread so that
people can easily
The mailing lists already exist.
However the podling status files are out of date so clutch cannot find
the information it needs.
See aso https://incubator.apache.org/projects/resilientdb.html which
is rather out of date.
On Wed, 21 Feb 2024 at 00:22, tison wrote:
>
> Hi Mohammad,
>
> For this
On Wed, 21 Feb 2024 at 00:28, tison wrote:
>
> Hi Dave,
>
> > One approach is to find good examples of each build technique. If you look
> > back at older projects you will see various historical waves of technique.
>
> I agree, and that's why I'd prefer a multi branches solution with a
>
