One thing we can take here is that perhaps we should think more about what
> meta-info should go into commits.
> One useful, and currently missing, field would the tag of the release it
> was merged in.
>
A year or two ago I was hoping to do a relatively easy fix to Volker's
scripts to auto
One thing we can take here is that perhaps we should think more about what
meta-info should go into commits.
One useful, and currently missing, field would the tag of the release it
was merged in.
Another would be the name of the reviewer.
We are also seeing that in our setting we have so many bra
On Friday, 15 December 2017 03:48:43 UTC-7, Dima Pasechnik wrote:
>
>
>
> On Friday, December 15, 2017 at 7:26:24 AM UTC, Dima Pasechnik wrote:
>>
>> On Fri, Dec 15, 2017 at 5:34 AM, Andrey Novoseltsev > > wrote:
>> > On Thursday, 14 December 2017 07:19:26 UTC-7, Dima Pasechnik wrote:
>> >>
>> >
On Friday, December 15, 2017 at 7:26:24 AM UTC, Dima Pasechnik wrote:
>
> On Fri, Dec 15, 2017 at 5:34 AM, Andrey Novoseltsev
> wrote:
> > On Thursday, 14 December 2017 07:19:26 UTC-7, Dima Pasechnik wrote:
> >>
> >> On Thu, Dec 14, 2017 at 12:38 PM, Volker Braun
> wrote:
> >> > I thought
git ls-remote trac | grep
;-)
On Friday, December 15, 2017 at 6:34:11 AM UTC+1, Andrey Novoseltsev wrote:
>
> User interface - whenever it is supposed to show all available branches
> having everything from trac makes it completely incomprehensible. So I
> personally think that "the official r
I created 2 blocker tickets for problems reported by some patchbots:
- #24376: Upgrade notedown
- #24378: Doctest failures related to sympy
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails
