On Sat, Jun 5, 2021 at 4:22 AM Mark Millard wrote:
>
>
> On 2021-Jun-5, at 04:09, Jan Beich wrote:
>
> > Mark Millard writes:
> >
> >> On 2021-Jun-5, at 03:10, Jan Beich wrote:
> >> It does appear that getting to all the individual-port
> >> information requires going to the Server and finding
On Thu, Jun 3, 2021 at 7:58 PM Jan Beich wrote:
> Kevin Oberman writes:
>
> > When ports were in svn, the revision caused a listing of package builds
> to
> > be listed in order by default, but now git hashes are used and the order
> > seems effectively random. There is no column for start time
On 2021-Jun-5, at 04:09, Jan Beich wrote:
> Mark Millard writes:
>
>> On 2021-Jun-5, at 03:10, Jan Beich wrote:
>> It does appear that getting to all the individual-port
>> information requires going to the Server and finding
>> the matching build there. Clicking on a Build link
>> in https
Mark Millard writes:
> On 2021-Jun-5, at 03:10, Jan Beich wrote:
> It does appear that getting to all the individual-port
> information requires going to the Server and finding
> the matching build there. Clicking on a Build link
> in https://pkg-status.freebsd.org/?all=1 gets to
> something foc
On 2021-Jun-5, at 03:10, Jan Beich wrote:
> Mark Millard via freebsd-ports writes:
>
>> On 2021-Jun-4, at 22:11, Kevin Oberman wrote:
>>
>>> . . .
>>>
>>> Sorry. I now see that I was unclear, but you seem to have figured it
>>> out. I believe that I am aware of all of the things you menti
Mark Millard via freebsd-ports writes:
> On 2021-Jun-4, at 22:11, Kevin Oberman wrote:
>
>> . . .
>>
>> Sorry. I now see that I was unclear, but you seem to have figured it
>> out. I believe that I am aware of all of the things you mention but
>> I can't find a way to track back beyond the curr
On 2021-Jun-4, at 22:11, Kevin Oberman wrote:
> . . .
>
> Sorry. I now see that I was unclear, but you seem to have figured it out. I
> believe that I am aware of all of the things you mention but I can't find a
> way to track back beyond the current build, the only one marked as
> "parall
On Thu, Jun 3, 2021 at 8:05 PM Mark Millard wrote:
> Kevin Oberman wrote on
> Date: Thu, 3 Jun 2021 15:49:47 -0700 :
>
> > When ports were in svn, the revision caused a listing of package builds
> to
> > be listed in order by default, but now git hashes are used and the order
> > seems effective
On 2021-Jun-3, at 20:05, Mark Millard wrote:
> Kevin Oberman wrote on
> Date: Thu, 3 Jun 2021 15:49:47 -0700 :
>
>> When ports were in svn, the revision caused a listing of package builds to
>> be listed in order by default, but now git hashes are used and the order
>> seems effectively rand
Kevin Oberman wrote on
Date: Thu, 3 Jun 2021 15:49:47 -0700 :
> When ports were in svn, the revision caused a listing of package builds to
> be listed in order by default, but now git hashes are used and the order
> seems effectively random. There is no column for start time and the
> elapsed ti
Kevin Oberman writes:
> When ports were in svn, the revision caused a listing of package builds to
> be listed in order by default, but now git hashes are used and the order
> seems effectively random. There is no column for start time and the
> elapsed time column is blank.
See also https://gi
When ports were in svn, the revision caused a listing of package builds to
be listed in order by default, but now git hashes are used and the order
seems effectively random. There is no column for start time and the
elapsed time column is blank.
Is there any simple way to look at the log of recen
12 matches
Mail list logo
