Hi Guix!
I've recently hacked a bit on Guile to try to make the output when using
(set! %load-verbosely #t) in e.g. (guix config) more helpful; giving it
a second dimension (the depth at which modules are loaded). It works,
but the default %load-hook needs to be refined as it uses too much
Am Freitag, dem 08.09.2023 um 22:24 +0200 schrieb Ricardo Wurmus:
>
> Liliana Marie Prikler writes:
>
> > > On Github, Pull Request branches are like our WIP branches. They
> > > are how we arrive at acceptable changes. Picky people like me
> > > would then go back and write new atomic
Am Freitag, dem 08.09.2023 um 17:39 +0200 schrieb Ricardo Wurmus:
>
> Liliana Marie Prikler writes:
>
> > To be completely honest, mumi recalling everything at 0 precision
> > is my biggest pet peeve at the moment
>
> Can you please make a test case for this and add it to the mumi
> tests? We
Thanks, I'll take a look once I find the time to look into sphinx failures.
best,
jgart
Liliana Marie Prikler writes:
> Am Freitag, dem 08.09.2023 um 17:27 +0200 schrieb Ricardo Wurmus:
>> I have the same positive view on our faux ChangeLogs commit messages,
>> though I also would like to have them generated. The benefit is
>> still there: I still get to *review* an effective
On 2023-09-08 21:26:56 +0200, Julien Lepiller wrote:
> Hi Andy,
>
> Thanks for the report! You might need a more recent po4a for it to work
> properly. Could try to guix pull, and enter a new shell for building guix?
>
> Le 8 septembre 2023 20:43:05 GMT+02:00, Andy Tai a écrit :
> >Checking
Liliana Marie Prikler writes:
>> On Github, Pull Request branches are like our WIP branches. They are
>> how we arrive at acceptable changes. Picky people like me would then
>> go back and write new atomic commits for the effective diff, but in
>> my role as a reviewer I usually rebase,
Hi Andy,
Thanks for the report! You might need a more recent po4a for it to work
properly. Could try to guix pull, and enter a new shell for building guix?
Le 8 septembre 2023 20:43:05 GMT+02:00, Andy Tai a écrit :
>Checking out the latest origin/master head, building guix fails:
>
>make[2]:
Am Freitag, dem 08.09.2023 um 17:27 +0200 schrieb Ricardo Wurmus:
> I have the same positive view on our faux ChangeLogs commit messages,
> though I also would like to have them generated. The benefit is
> still there: I still get to *review* an effective summary of the
> changes before pushing
Hi,
Am Freitag, dem 08.09.2023 um 16:44 +0200 schrieb Ricardo Wurmus:
> I often have to review Github Pull Requests, and I don’t go commit by
> commit by go through the diff and annotate the changes. I *read* the
> commits to get a sense for how the feature evolved and why changes
> were made,
Checking out the latest origin/master head, building guix fails:
make[2]: Entering directory '/share/software/guix/guix.git/po/packages'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/share/software/guix/guix.git/po/packages'
make[2]: Entering directory
Am Freitag, dem 08.09.2023 um 11:16 +0200 schrieb Giovanni Biscuolo:
> [...]
>
> > > On 2023-09-06, Liliana Marie Prikler wrote:
>
> [...]
>
> > > > It's
> > > >
> > > > * file (variable)[field]{do you need 4
> > > > levels?}
>
> The general form of a ChangeLog Style format for Guix code
Hello Efraim,
Efraim Flashner writes:
> On Fri, Sep 08, 2023 at 11:53:43AM +0200, Giovanni Biscuolo wrote:
> That wasn't my read of it at all.
I don't understand what part of my message is different from your read,
so I cannot comment
> I too have many packages which I haven't upstreamed.
Giovanni Biscuolo writes:
> […] actually Debbugs or Mumi web
> interfaces are read-only: you cannot open a bug report or comment it,
> you have to send an email; this is a _feature_, not a bug since we don't
> need a _complex_ web based authentication+authorization system for bug
>
"jgart" writes:
> What is the cadence for merging the python-team branch into master?
>
> Should you do it, me, or someone else?
Another thing that needs fixing is sphinx. The upgrade of
python-pygments and python-sphinx did not go over too well.
--
Ricardo
Liliana Marie Prikler writes:
> To be completely honest, mumi recalling everything at 0 precision is my
> biggest pet peeve at the moment
Can you please make a test case for this and add it to the mumi tests?
We have tests for the search feature there.
--
Ricardo
Maxim Cournoyer writes:
> I used to think the same about ChangeLogs style commit messages, but I
> have to admit that it forces some discipline on me by having me review
> my changes in details and write out what I did. It'll sometimes expose
> something that'd be better kept in a separate
Liliana Marie Prikler writes:
>> one fundamental issue with the email based workflow is that its
>> underlying data model simply does not formally encode enough
>> information to be able to implement a slick workflow and frontend.
>> e.g. with a PR based model the obsolete versions of a PR is
Josselin Poiret writes:
> Regarding the “mom argument”, I would disagree and say that this is
> completely related: interruptions are more costly, you're more likely to
> have less attention span, and overall you probably don't want to commit
> to 20 steps just to send a contribution.
That’s
Hi,
What does the integration and testing work involve?
Is the work/details for what's required for that documented for someone doing
that work or is it just a matter of successfully building all dependents that
you are introducing against master?
best,
jgart
Ricardo,
Ricardo Wurmus writes:
> Giovanni,
>
>> You are obviously free not to contribute your patches upstream but the
>> fact that you decided not to because it's "too hard" (my executive
>> summary about your complaints about Change Log content rules) to write
>> commit messages suitable for
On Fri, Sep 08, 2023 at 11:53:43AM +0200, Giovanni Biscuolo wrote:
> Hello Katherine,
>
> Katherine Cox-Buday writes:
>
> [...]
>
> > By "standard" I mean the GNU Changelog format
> > (https://www.gnu.org/prep/standards/standards.html#Change-Logs). As
> > in: it's expected that commit messages
Giovanni,
> You are obviously free not to contribute your patches upstream but the
> fact that you decided not to because it's "too hard" (my executive
> summary about your complaints about Change Log content rules) to write
> commit messages suitable for contribution it _not_ a Guix
On 2023-09-08 11:47:56 +0200, Wojtek Kosior wrote:
> Hello Josselin
>
> > wolf writes:
> >
> > > Hmm, but the recipe for the authenticate rule comes from the (possibly)
> > > compromised source, no? So the attacker can just modify the recipe
> > > instead of
> > > the command going the
Hi!
Simon Tournier writes:
[...]
> For example, we communicate in English. It appears to me impossible to
> send a contribution without having some basic knowledge of English.
And, believe me or not, for me /that/ is a **significant** cognitive
overhead not just to contribute to
Hello Katherine,
Katherine Cox-Buday writes:
[...]
> By "standard" I mean the GNU Changelog format
> (https://www.gnu.org/prep/standards/standards.html#Change-Logs). As
> in: it's expected that commit messages use this format.
[...]
> In my response I was trying to point out a flaw in your
Hello Josselin
> wolf writes:
>
> > Hmm, but the recipe for the authenticate rule comes from the (possibly)
> > compromised source, no? So the attacker can just modify the recipe instead
> > of
> > the command going the authentication. Am I missing something?
>
> You can use a previously
Hi all!
I think the discussion about ChangeLog Style shows we probably need to:
1. enhance the manual section "22.6 Submitting Patches"
https://guix.gnu.org/en/manual/devel/en/html_node/Submitting-Patches.html
--8<---cut here---start->8---
Please write
Hi,
wolf writes:
> Hmm, but the recipe for the authenticate rule comes from the (possibly)
> compromised source, no? So the attacker can just modify the recipe instead of
> the command going the authentication. Am I missing something?
You can use a previously trusted guix to do the
Hi,
> What is the cadence for merging the python-team branch into master?
> Should you do it, me, or someone else?
there’s no timeline or schedule. It happens when someone does the
integration and testing work. I don’t have the time to do this right
now, so please go ahead.
Note there’s also
Hi,
> What is the git approach for keeping the Python branch up to date? 閭
> Should I be rebasing off of master or something else?
yeah, that’s generally what I would do before working on it. Note that
you cannot force-push into Savannah. You have to remove the remote branch
and create it again.
Simon Tournier writes:
> Since I am French and it is easier for me to comment about my
> disagreements than the converse. ;-)
Feels like literally every national group makes this up about
themselves; British people are stereotypically very prone to
complaining, too :P
-- (
32 matches
Mail list logo
