Hi Simon, Chris,
Simon Tournier writes:
> Hi Chris, all,
>
> On Wed, 06 Sep 2023 at 16:55, Christopher Baines wrote:
>
>> Once we know what tags to use, I can have the QA frontpage do something
>> similar to the "Mark as moreinfo" links, so it's easy to just click a
>> button then send the
Hi,
Simon Tournier writes:
> Hi,
>
> On Wed, 06 Sep 2023 at 12:14, Maxim Cournoyer
> wrote:
>
>>> Let's avoid manual gardening as much as possible! :-)
>>
>> I like the idea!
>
> I think that automatizing is not trivial. Sadly.
>
> There are many corner cases:
>
> 1. series as attachement
>
Hi Chris, all,
On Wed, 06 Sep 2023 at 16:55, Christopher Baines wrote:
> Once we know what tags to use, I can have the QA frontpage do something
> similar to the "Mark as moreinfo" links, so it's easy to just click a
> button then send the email to change the state of a issue.
That’s cool!
Hi Felix,
On Wed, 06 Sep 2023 at 12:01, Felix Lechner via "Development of GNU Guix and
the GNU System distribution." wrote:
> Usually, helpful reviews come from people with more experience. In
> your system they come from folks with less. That seems upside down to
> me.
Well, I think we are
Hi,
On Wed, 06 Sep 2023 at 12:14, Maxim Cournoyer wrote:
>> Let's avoid manual gardening as much as possible! :-)
>
> I like the idea!
I think that automatizing is not trivial. Sadly.
There are many corner cases:
1. series as attachement
2. not all the series is applied
3. commit message
Hi Josselin,
On Wed, 06 Sep 2023 at 11:45, Josselin Poiret wrote:
>> Well, on my machine, the bigger bottleneck seems the procedure name
>> ’proxy’ which copies stuff around, IIUC. See [1].
>
> Proxy is on the helper script side, it's just waiting for the actual
> build script to do its thing.
Hello,
On 2023-09-06 04:49, Maxim Cournoyer wrote:
Hi Katherine,
Katherine Cox-Buday writes:
On 9/5/23 10:01 AM, Simon Tournier wrote:
Well, somehow, I consider the commit message format similarly as
coding
style. We can discuss which one is better than the other when at the
end it only
Hello,
I wanted to add to this thread my 2 cents. As a person who has recently
(last months) made the first attempts at contributing.
To me, registrations and reliance on JS had always been an obstacle to
using web-based forges. This is one of the reasons I haven't been
contributing to existing
Am Mittwoch, dem 06.09.2023 um 10:52 -0700 schrieb Vagrant Cascadian:
> I always get tripped up with phases, modify-phases, etc. as there
> seem to be potentially four or more levels deep in some common code
> patterns... for example, a recent commit mentioning phases:
>
> commit
Hi Chris,
On Wed, Sep 6, 2023 at 11:39 AM Christopher Baines wrote:
>
> I don't want to make reviewing changes more difficult, and I think
> setting up more people with commit access and continuing the trend that
> it's mostly people with commit access that review changes would increase
> the
Maxim Cournoyer writes:
> Hi Vagrant,
>
> Vagrant Cascadian writes:
>
>> On 2023-09-06, Liliana Marie Prikler wrote:
>>> Am Dienstag, dem 05.09.2023 um 19:41 -0400 schrieb brian
‘* foo/bar.scm new-package (inputs): add input’
stuff. I literally can never remember this format,
Am Dienstag, dem 05.09.2023 um 20:34 -0600 schrieb Katherine Cox-Buday:
> In the US, the phrase "I don't buy it" is usually the response to
> someone trying to trick you into something. This is a little hurtful
> because it's either saying:
>
> "You have an ulterior motive and are trying to
Hi,
I've made the change proposed and tested; then installed as 65dcfb3f
(".dir-locals: Streamline Geiser configuration."). Let me know if
you encounter any problem.
--
Thanks,
Maxim
Am Mittwoch, dem 06.09.2023 um 00:04 +0200 schrieb wolf:
> On 2023-09-05 22:43:04 +0200, Liliana Marie Prikler wrote:
> > Am Dienstag, dem 05.09.2023 um 19:40 +0100 schrieb (:
> > > Liliana Marie Prikler writes:
> > > > Uhm, we have snippets?
> > >
> > > Well, those are exclusive to Emacs :)
Felix Lechner writes:
> On Wed, Sep 6, 2023 at 9:47 AM Christopher Baines wrote:
>>
>> Maybe we can use debbugs tags for this?
>
> Instead of pushing people into reviews and then again making the same
> committers a bottleneck, I would offer some entry-level contributors
> commit rights but
Hi Vagrant,
Vagrant Cascadian writes:
> On 2023-09-06, Liliana Marie Prikler wrote:
>> Am Dienstag, dem 05.09.2023 um 19:41 -0400 schrieb brian
>>> ‘* foo/bar.scm new-package (inputs): add input’
>>>
>>> stuff. I literally can never remember this format, no matter how many
>>> times I do it.
Hi Chris,
On Wed, Sep 6, 2023 at 9:47 AM Christopher Baines wrote:
>
> Maybe we can use debbugs tags for this?
Instead of pushing people into reviews and then again making the same
committers a bottleneck, I would offer some entry-level contributors
commit rights but require that they obtain
On 2023-09-06, Liliana Marie Prikler wrote:
> Am Dienstag, dem 05.09.2023 um 19:41 -0400 schrieb brian
>> ‘* foo/bar.scm new-package (inputs): add input’
>>
>> stuff. I literally can never remember this format, no matter how many
>> times I do it. I'm reasonably sure square brackes go in there
Am Dienstag, dem 05.09.2023 um 19:41 -0400 schrieb brian
> ‘* foo/bar.scm new-package (inputs): add input’
>
> stuff. I literally can never remember this format, no matter how many
> times I do it. I'm reasonably sure square brackes go in there some
> where. It can take me quite a while to put
Hey!
I've been reviewing the list of ideas on and around QA ([1]) recently,
and got thinking again about how to support people without commit access
reviewing patches. Obviously you don't need commit access to review
patches, but where I think we need some process is how to expedite
someone with
Hi Giovanni,
Giovanni Biscuolo writes:
> Hello,
>
> often bug reports related to patches are left open even after the
> patch/patchset have been applied, the last example is a batch of Debbugs
> manual gardening from Vagrant last Fri and Sat when he closed more than
> 20 bugs with messages
Hi,
Attila Lendvai writes:
>> also not as obvious (you search for lines added or removed or changed,
>> not easy language such as 'gnu: package-name: Add').
>
>
> i'm pretty sure that the source of the annoyance is not the strict
> format in the summary line, but the formal details in the
Hello,
related to this thread, I just came across an entry in Cory Doctorow's blog:
https://pluralistic.net/2023/08/18/openwashing/#you-keep-using-that-word-i-do-not-think-it-means-what-you-think-it-means
It is already interesting in its disection of the terms "open" vs. "free",
which is
Adam Faiz wrote:
> On 8/20/23 19:35, B. Wilson wrote:
> > Hello Guix,
> >
> > Knee deep in CMake hell here and would appreciate a helping hand. ArrayFire
> > build is defeating me:
> >
> > CMake Error at
> >
> > also not as obvious (you search for lines added or removed or changed,
> > not easy language such as 'gnu: package-name: Add').
>
>
>
> i'm pretty sure that the source of the annoyance is not the strict format in
> the summary line, but the formal details in the commit message body.
On Mon, Sep 04, 2023 at 09:27:44AM +, Guillaume Le Vaillant wrote:
> Hi.
> I created a lisp-team branch to work one some updates for clisp and
> sbcl. Could someone with admin access to the CI things add a job for it?
> Thanks.
I commented on IRC but figured I should post to the mailing list.
> also not as obvious (you search for lines added or removed or changed,
> not easy language such as 'gnu: package-name: Add').
i'm pretty sure that the source of the annoyance is not the strict format in
the summary line, but the formal details in the commit message body.
--
• attila lendvai
Hi Katherine,
On Tue, 05 Sep 2023 at 20:58, Katherine Cox-Buday
wrote:
> OK, great! What are next steps, and how can I help?
Well, from my point of view, the next steps are:
+ Propose a survey (questions), open a new thread (or a bug report) for
iterating.
+ Review how to distribute the
Hi Katherine,
( I feel we are not able to communicate on commit message format and
it seems we are on a road that leads to unfruitful output. Well, I
appreciate the discussion and I have carefully read the messages. )
On Tue, 05 Sep 2023 at 20:34, Katherine Cox-Buday
wrote:
> For
Giovanni Biscuolo writes:
> Hello,
>
> often bug reports related to patches are left open even after the
> patch/patchset have been applied, the last example is a batch of Debbugs
> manual gardening from Vagrant last Fri and Sat when he closed more than
> 20 bugs with messages similar to this
Hi Simon,
Simon Tournier writes:
> Hi Josselin,
>
> On Tue, 29 Aug 2023 at 13:58, Josselin Poiret wrote:
>
>> After looking a bit more into guix pull speed, or to be more precise the
>> "Computing Guix derivation..." step, which is not substitutable. I've
>> come to the conclusion that the
Hi Lily,
Liliana Marie Prikler writes:
> Instead, we have seen in this thread appeals to age, appeals to
> perceived lack of personal benefit, and now appeals to typing effort,
> none of which really make that great of an argument against the
> ChangeLog style, especially when they come in
Hello,
often bug reports related to patches are left open even after the
patch/patchset have been applied, the last example is a batch of Debbugs
manual gardening from Vagrant last Fri and Sat when he closed more than
20 bugs with messages similar to this one:
--8<---cut
33 matches
Mail list logo
