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 co
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 created
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 fol
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
> default
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
default branch containing README for redirects.
>From another pe
Hi Tison,
I’m following along. Infrastructure has a Pelican template site that is out of
date: https://github.com/apache/template-site/
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.
Best,
Da
Hi Dave,
Thanks for picking up this commit. You may join the discussion at [1].
I have all the permission to follow what I want. But since
apache-website-template is technically a foundation-wise repo and I'm
a newcomer here, I'd like to listen to people's opinions before moving
forward; especial
From the commit email it looks like this repository belongs to the Incubator.
> On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> tison pushed a change to branch jekyll
> in repository https://gitbox.apache.org/repos/
Let me look at it in the morning, I thought all IPMC or even committers
could push, but I double check and make sure it’s properly configured.
On Sun, Dec 16, 2018 at 19:32 Julian Hyde wrote:
> Who owns the https://github.com/apache/apache-website-template/ repo?
> I thought (perhaps mistakenly)
On Sat, Dec 5, 2015 at 12:20 PM, Julian Hyde wrote:
> Thanks, Luciano. I've got a couple of issues to discuss, which I'll
> log as github issues, so we can discuss there.
>
> Julian
>
>
>
Great, I have created a JIRA issue to enable issues for the repository
https://issues.apache.org/jira/browse
Thanks, Luciano. I've got a couple of issues to discuss, which I'll
log as github issues, so we can discuss there.
Julian
On Fri, Dec 4, 2015 at 10:37 PM, Luciano Resende wrote:
> I have merged your changes now, and will push as soon as a fix couple
> little navigation issues.
>
> Thanks.
>
> O
I have merged your changes now, and will push as soon as a fix couple
little navigation issues.
Thanks.
On Friday, December 4, 2015, Julian Hyde wrote:
> I’ve been making some changes to the template and submitting them as
> github pull requests. (I made 5 pull requests a couple of weeks ago, w
I’ve been making some changes to the template and submitting them as github
pull requests. (I made 5 pull requests a couple of weeks ago, which weren’t
noticed, and Luciano subsequently made very some similar changes. Frustrating.)
I don’t want to clutter this list with dev traffic, but there’s
On Thu, Dec 3, 2015 at 6:16 AM, Marvin Humphrey
wrote:
> On Thu, Dec 3, 2015 at 5:17 AM, sebb wrote:
> > PING
>
> I'd also like to see this addressed. Licensing documentation for Incubator
> sample code should adhere to best practices.
>
> > On 28 November 2015 at 22:59, sebb wrote:
> >> On 28
ith the same copyright details.
>
>Regards,
>Roberta
>
>-Original Message-
>From: Marvin Humphrey [mailto:mar...@rectangular.com]
>Sent: Thursday, December 3, 2015 6:16 AM
>To: general@incubator.apache.org
>Cc: lrese...@apache.org
>Subject: Re: apache-website-
do
it differently, even with the same copyright details.
Regards,
Roberta
-Original Message-
From: Marvin Humphrey [mailto:mar...@rectangular.com]
Sent: Thursday, December 3, 2015 6:16 AM
To: general@incubator.apache.org
Cc: lrese...@apache.org
Subject: Re: apache-website-template git commit
On Thu, Dec 3, 2015 at 5:17 AM, sebb wrote:
> PING
I'd also like to see this addressed. Licensing documentation for Incubator
sample code should adhere to best practices.
> On 28 November 2015 at 22:59, sebb wrote:
>> On 28 November 2015 at 16:26, wrote:
>>> +The following components includ
PING
On 28 November 2015 at 22:59, sebb wrote:
> On 28 November 2015 at 16:26, wrote:
>> Repository: apache-website-template
>> Updated Branches:
>> refs/heads/master b140c230c -> 9e881e247
>>
>>
>> Add LICENSE and NOTICE files
>>
>> Properly document LICENSE for each component
>> included on
On 28 November 2015 at 16:26, wrote:
> Repository: apache-website-template
> Updated Branches:
> refs/heads/master b140c230c -> 9e881e247
>
>
> Add LICENSE and NOTICE files
>
> Properly document LICENSE for each component
> included on this website, including necessary
> required attribution no
20 matches
Mail list logo
