Greetings,
I've created https://reviews.freebsd.org/D38382 to encourage more people to
submit pull requests for simple fixes.
A simple fix is one that's brief, easily reviewed in a few minutes, ready
to land in the tree (or nearly so) and
has all the normal 'curation' done: author name is set
On 30/01/2023 21:09, Dmitry Salychev wrote:
Maybe, but my laziness won't let me keep it that simple :)
https://reviews.freebsd.org/H185 should do the trick, I think.
404 for me.
Warner Losh writes:
…
OpenPGP_signature
Description: OpenPGP digital signature
On 01/02/2023 06:05, Yetoo wrote:
On Tue, Jan 31, 2023, 9:47 AM David Chisnall wrote:
On 30/01/2023 21:39, Yetoo wrote:
If github is going to be considered for issue tracking I just want to
say, after having extensively using it for issue tracking, it tends to
be difficult to find an issue if
Mitchell Horne writes:
On 1/31/23 04:52, Stephane Rochoy wrote:
Mitchell Horne writes:
[Src] Needs Reviewer
https://reviews.freebsd.org/differential/query/65AoyPFlIhdE/
What is the purpose of the "Contributor Reviews (base)"
project/group?
Regards,
-- Stéphane Rochoy
O: Stormshield
On Tue, Jan 31, 2023, 9:47 AM David Chisnall wrote:
>
> On 30/01/2023 21:39, Yetoo wrote:
> >
> > If github is going to be considered for issue tracking I just want to
> > say, after having extensively using it for issue tracking, it tends to
> > be difficult to find an issue if the exact title
> On 31. Jan 2023, at 22:44, Kurt Jaeger wrote:
>
> Hi!
>
This can be as easy as moving everything into Phabricator.
>>> There's the issue that Phabricator itself is no longer supported
>>> upstream:
> [...]
>>> https://we.phorge.it/
>
>> Should be no harder than regular update. They
Hi!
> > > This can be as easy as moving everything into Phabricator.
> > There's the issue that Phabricator itself is no longer supported
> > upstream:
[...]
> > https://we.phorge.it/
> Should be no harder than regular update. They even have a HOWTO
>
On 30/01/2023 21:39, Yetoo wrote:
If github is going to be considered for issue tracking I just want to
say, after having extensively using it for issue tracking, it tends to
be difficult to find an issue if the exact title isn't entered and many
duplicate reports are made as a result. Code
On 1/31/23 04:52, Stephane Rochoy wrote:
Mitchell Horne writes:
[Src] Needs Reviewer
https://reviews.freebsd.org/differential/query/65AoyPFlIhdE/
What is the purpose of the "Contributor Reviews (base)"
project/group?
Regards,
--
Stéphane Rochoy
O: Stormshield
It is a group ("Project")
Mitchell Horne writes:
[Src] Needs Reviewer
https://reviews.freebsd.org/differential/query/65AoyPFlIhdE/
What is the purpose of the "Contributor Reviews (base)"
project/group?
Regards,
--
Stéphane Rochoy
O: Stormshield
My two cents...
I think some of the integration issues can be resolved with some rule
changes and showing those relevant rules that people will see every time
they make a pull request, report, etc... as I think what will happen with
each item is too uncertain even if there was automation. I think
El lun., 30 ene. 2023 18:06, ykla escribió:
> Hi,
>
> The documentation project on reviews.freebsd.org is also very inactive.
> For example, it's been almost 3 months since I submitted my revision -
> https://reviews.freebsd.org/D37322. After I submitted it, it was neither
> reviewed nor
Maybe, but my laziness won't let me keep it that simple :)
https://reviews.freebsd.org/H185 should do the trick, I think.
Warner Losh writes:
> I think just "sys/dev/dpaa2" is all you need when adding the Herald rule. :)
>
> More generally, no, there's no way that I've found to only match
On 1/30/23 13:32, User Ngor wrote:
On 1/30/23 13:53, Warner Losh wrote:
On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
Hi,
On 1/30/23 02:54, Julian H. Stacey wrote:
The main idea: to prevent information fragmentation and improve
discoverability, cross-referencing
On 1/30/23 13:53, Warner Losh wrote:
On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
Hi,
On 1/30/23 02:54, Julian H. Stacey wrote:
The main idea: to prevent information fragmentation andimprove
discoverability, cross-referencing abilities, search, etc.
With regards to
Hi,
The documentation project on reviews.freebsd.org is also very inactive. For
example, it's been almost 3 months since I submitted my revision -
https://reviews.freebsd.org/D37322. After I submitted it, it was neither
reviewed nor approved for a long time. Now, due to changes in the FreeBSD
On 1/30/23 10:08, Kurt Jaeger wrote:
Hi!
ihor@antonovs.family wrote:
This can be as easy as moving everything into Phabricator.
There's the issue that Phabricator itself is no longer supported
upstream:
https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
I think just "sys/dev/dpaa2" is all you need when adding the Herald rule. :)
More generally, no, there's no way that I've found to only match files that
match certain regexp.
Warner
On Mon, Jan 30, 2023 at 9:49 AM Dmitry Salychev wrote:
>
> Warner Losh writes:
>
> > On Mon, Jan 30, 2023 at
Warner Losh writes:
> On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote:
>
> Hi,
>
> Kurt Jaeger writes:
>
> > Hi,
> >
> >> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >> >The main idea: to prevent information fragmentation andimprove
> >> >discoverability,
Hi folks,
I'd like to first of all thank Warner for all his hard work. Working on
infrastructure can seem like pretty thankless work.
As an outsider to FreeBSD, but not an outsider to the workings of FLOSS
organisations, I just want to remind everyone of one core issue: It's usually
insiders,
On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote:
>
> Hi,
>
> Kurt Jaeger writes:
>
> > Hi,
> >
> >> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >> >The main idea: to prevent information fragmentation andimprove
> >> >discoverability, cross-referencing abilities, search, etc.
Warner Losh writes:
> On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
>
> Hi,
>
> > > On 1/30/23 02:54, Julian H. Stacey wrote:
> > >The main idea: to prevent information fragmentation andimprove
> > >discoverability, cross-referencing abilities, search, etc.
> >
> >
Kurt Jaeger writes:
If you know phabricator in more detail, is there any kind of
tool to understand the activity going on ?
In bugs.freebsd.org, there is the dashboard:
https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html
I think we might need something similar to help us
Hi,
Kurt Jaeger writes:
> Hi,
>
>> > On 1/30/23 02:54, Julian H. Stacey wrote:
>> >The main idea: to prevent information fragmentation andimprove
>> >discoverability, cross-referencing abilities, search, etc.
>>
>> With regards to improving discoverability, Phabricator's Owner
>>
On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
> Hi,
>
> > > On 1/30/23 02:54, Julian H. Stacey wrote:
> > >The main idea: to prevent information fragmentation andimprove
> > >discoverability, cross-referencing abilities, search, etc.
> >
> > With regards to improving
Hi,
> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >The main idea: to prevent information fragmentation andimprove
> >discoverability, cross-referencing abilities, search, etc.
>
> With regards to improving discoverability, Phabricator's Owner
> tool could be a good tactical move:
Hello,
> I had a similar thing happen to me, the mailing list FreeBSD-doc seemed to
> exist as if no one existed, and there was no one posting in it except for
> the automated bug reports from the bots.
> I have not had any replies to my several posts either.
> So can the admins tell how many
Hi,
I had a similar thing happen to me, the mailing list FreeBSD-doc seemed to
exist as if no one existed, and there was no one posting in it except for
the automated bug reports from the bots. I have not had any replies to my
several posts either. So can the admins tell how many people actually
Hi!
ihor@antonovs.family wrote:
> This can be as easy as moving everything into Phabricator.
There's the issue that Phabricator itself is no longer supported
upstream:
https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
https://github.com/phacility/phabricator
User Ngor writes:
On 1/30/23 02:54, Julian H. Stacey wrote:
The main idea: to prevent information fragmentation and
improve
discoverability, cross-referencing abilities, search, etc.
With regards to improving discoverability, Phabricator's Owner
tool could be a good tactical
On 1/30/23 02:54, Julian H. Stacey wrote:
> Jamie Landeg-Jones wrote:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 is a
trivial fix
>> to an admittedly trivial issue, but it's soon going to hit one year old,
>> and has not had any feedback. Not even "this is rubbish. close
31 matches
Mail list logo
