+1 for the change. It is still pretty readable on any edtor.
-- Originalnachricht --
Von rbo...@rcbowen.com
An "dev@httpd.apache.org"
Datum 24.01.2024 16:06:43
Betreff PR #363
I've been poking at some of our open PRs looking for docs-only changes
that we can possibly cle
+1
On Thu, Jan 25, 2024 at 3:45 PM Eric Covener wrote:
>
> I wouldn't mind move/rename to README.md
>
> On Thu, Jan 25, 2024, 10:40 AM Joe Orton wrote:
>>
>> On Thu, Jan 25, 2024 at 08:12:24AM +0100, Ruediger Pluem wrote:
>> > Tried it in r1915391 and it seems to work. Not sure if there are
>>
I wouldn't mind move/rename to README.md
On Thu, Jan 25, 2024, 10:40 AM Joe Orton wrote:
> On Thu, Jan 25, 2024 at 08:12:24AM +0100, Ruediger Pluem wrote:
> > Tried it in r1915391 and it seems to work. Not sure if there are
> > general downsides / objections with regards to symlinks in our
> >
On Thu, Jan 25, 2024 at 08:12:24AM +0100, Ruediger Pluem wrote:
> Tried it in r1915391 and it seems to work. Not sure if there are
> general downsides / objections with regards to symlinks in our
> repository. But trunk is CTR :-).
Oh, that looks really nice. +1
Thanks to you, Rich, and Mayank
On 1/25/24 8:04 AM, Ruediger Pluem wrote:
>
>
> On 1/24/24 11:31 PM, Rich Bowen wrote:
>> Well, it turns out that in order for this to actually work, we would need to
>> rename README to README.md, so I'm inclined to revert
>> this change unless someone thinks differently.
>
> How about
On 1/24/24 11:31 PM, Rich Bowen wrote:
> Well, it turns out that in order for this to actually work, we would need to
> rename README to README.md, so I'm inclined to revert
> this change unless someone thinks differently.
How about using a symlink? Keep README and create a README.md symlink
ges
> that we can possibly clean up.
>
> PR #363 - https://github.com/apache/httpd/pull/363 - converts README
> from plaintext to markdown, and makes no other changes. This makes it
> prettier on GitHub.
>
> I almost just CTR'ed it, but it occurred to me that someone might find
&g
een poking at some of our open PRs looking for docs-only
> > > > changes
> > > > that we can possibly clean up.
> > > >
> > > > PR #363 - https://github.com/apache/httpd/pull/363 - converts
> > > > README
> > > > from plaintext to mar
hanges
> > > that we can possibly clean up.
> > >
> > > PR #363 - https://github.com/apache/httpd/pull/363 - converts
> > > README
> > > from plaintext to markdown, and makes no other changes. This
> > > makes it
> > > prettier on G
at 4:56 PM Mads Toftum wrote:
> >
> > On Wed, Jan 24, 2024 at 10:06:43AM -0500, rbo...@rcbowen.com wrote:
> > > I've been poking at some of our open PRs looking for docs-only changes
> > > that we can possibly clean up.
> > >
> > > PR #363 - https:
On Wed, Jan 24, 2024 at 4:56 PM Mads Toftum wrote:
>
> On Wed, Jan 24, 2024 at 10:06:43AM -0500, rbo...@rcbowen.com wrote:
> > I've been poking at some of our open PRs looking for docs-only changes
> > that we can possibly clean up.
> >
> > PR #363 - https://gi
On Wed, Jan 24, 2024 at 10:06:43AM -0500, rbo...@rcbowen.com wrote:
> I've been poking at some of our open PRs looking for docs-only changes
> that we can possibly clean up.
>
> PR #363 - https://github.com/apache/httpd/pull/363 - converts README
> from plaintext to markdown, and
I've been poking at some of our open PRs looking for docs-only changes
that we can possibly clean up.
PR #363 - https://github.com/apache/httpd/pull/363 - converts README
from plaintext to markdown, and makes no other changes. This makes it
prettier on GitHub.
I almost just CTR'ed
13 matches
Mail list logo
