Re: Committers available for Patch hacking/review meet-up?

2024-02-15 Thread Simon Tournier
Hi, On mar., 13 févr. 2024 at 14:48, Steve George wrote: > At Guix Days we said we'd organise some patch review sessions. Cool! > Anyone available? If you are and can put your name down for a particular > date that would be brilliant! I will do. Thanks for the initiative! > Q2: Does anyo

Re: Committers available for Patch hacking/review meet-up?

2024-02-15 Thread Steve George
On 15/02/2024 00:53, jgart wrote: 7th March (Thursday) 20th March (Wednesday) 2nd April (Tuesday) 15th April (Monday) 3rd May (Friday) 16th May (Thursday) 29th May (Wednesday) Each one held at 19:00 CET / 18:00 BST / 13:00 EST [0] for 1.5 hours. Hi, Thanks for putting this together. Lately I

Re: Committers available for Patch hacking/review meet-up?

2024-02-15 Thread Steve George
Hi Andreas, On 14/02/2024 14:04, Andreas Enge wrote: Hello, thanks, Steve, for getting things going! Am Tue, Feb 13, 2024 at 02:48:08PM + schrieb Steve George: We said they'd be every 13 days, for 3 months to see if it has interest. Proposed calendar: 7th March (Thursday) I will be arou

Re: Committers available for Patch hacking/review meet-up?

2024-02-14 Thread jgart
> 7th March (Thursday) > 20th March (Wednesday) > 2nd April (Tuesday) > 15th April (Monday) > 3rd May (Friday) > 16th May (Thursday) > 29th May (Wednesday) > > Each one held at 19:00 CET / 18:00 BST / 13:00 EST [0] for 1.5 hours. Hi, Thanks for putting this together. Lately I've been too busy w

Re: Committers available for Patch hacking/review meet-up?

2024-02-14 Thread Andreas Enge
Hello, thanks, Steve, for getting things going! Am Tue, Feb 13, 2024 at 02:48:08PM + schrieb Steve George: > We said they'd be every 13 days, for 3 months to see if it has interest. > Proposed calendar: > 7th March (Thursday) I will be around on this day. > 2nd April (Tuesday) > 15th April

Committers available for Patch hacking/review meet-up?

2024-02-13 Thread Steve George
Hi, At Guix Days we said we'd organise some patch review sessions. Q1: Can at least one committer uh ... commit to be at each session to help? The goal of of the sessions is: 1. Teaching people how to do patch reviews 2. Do some patch reviews together in a friendly hacking session We said the

Re: [PATCH] HACKING: Mention 'guix environment'.

2014-11-24 Thread Ludovic Courtès
David Thompson skribis: > Ludovic Courtès writes: > >> David Thompson skribis: >> >>> Just today I used 'guix environment guix' to quickly create a >>> development environment for Guix hacking. I figured it should be >>> mentioned in the HACKING file to assist developers that happen to >>> alr

Re: [PATCH] HACKING: Mention 'guix environment'.

2014-11-23 Thread David Thompson
Ludovic Courtès writes: > David Thompson skribis: > >> Just today I used 'guix environment guix' to quickly create a >> development environment for Guix hacking. I figured it should be >> mentioned in the HACKING file to assist developers that happen to >> already by using a Guix system. >> >>

Re: [PATCH] HACKING: Mention 'guix environment'.

2014-11-23 Thread Ludovic Courtès
David Thompson skribis: > Just today I used 'guix environment guix' to quickly create a > development environment for Guix hacking. I figured it should be > mentioned in the HACKING file to assist developers that happen to > already by using a Guix system. > > WDYT? Sure, please commit! I thou

[PATCH] HACKING: Mention 'guix environment'.

2014-11-23 Thread David Thompson
Sep 17 00:00:00 2001 From: David Thompson Date: Sun, 23 Nov 2014 08:06:21 -0500 Subject: [PATCH] HACKING: Mention 'guix environment'. --- HACKING | 6 ++ 1 file changed, 6 insertions(+) diff --git a/HACKING b/HACKING index 0231c7d..ad816aa 100644 --- a/HACKING +++ b/HACKING @@ -21,

Re: [PATCH] HACKING

2013-12-07 Thread Ludovic Courtès
John Darrington skribis: > commit feae92498356789d19883424cc078e8e8827626b > Author: John Darrington > Date: Sun Dec 1 08:28:54 2013 +0100 > > HACKING: Updated advice about possible errors in ./bootstrap process. > > Commit ff1cbb95383b25cf1d6b533c8a046329ee53d1db made errors due

[PATCH] HACKING

2013-12-06 Thread John Darrington
Patch for your consideration. -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. commit feae92498356789d19883424cc078e8e8827626b Author: John Darrington Date: Sun Dec 1 08:28