l...@gnu.org (Ludovic Courtès) skribis:
> The best patch-tracking candidate I’ve seen so far is “patches”, written
> by/for the QEMU people (the ‘patches’ package in Guix.)
>
> https://www.gnu.org/software/guix/packages/#patches
>
> I think it has everything most of us want, including an Emacs i
Cyril Roelandt skribis:
> I think we could have a mailing-list dedicated to these trivial update
> patches. I'd also be in favor of splitting the mailing-list into many
> smaller ones, such as:
> - core;
> - packages;
> - trivial updates.
I’m not sure it would help much because it is often quite
On Wed, Mar 30, 2016 at 10:52:15PM +0200, Cyril Roelandt wrote:
> On 03/21/2016 04:48 PM, Mathieu Lirzin wrote:
> > To automate the repetitive tasks, Cyril Roelandt had started sometimes
> > ago to work on a bot that was continuously applying and building
> > incoming patches on top of master and r
On 03/21/2016 04:48 PM, Mathieu Lirzin wrote:
> To automate the repetitive tasks, Cyril Roelandt had started sometimes
> ago to work on a bot that was continuously applying and building
> incoming patches on top of master and report (by email) if things were
> building correctly. I think that is a
Ludovic Courtès (2016-03-24 01:24 +0300) wrote:
> Alex Kost skribis:
>
>> Ricardo Wurmus (2016-03-23 10:41 +0300) wrote:
>>
>>> Chris Marusich writes:
>>>
While we're talking about patches, I'm curious: how are other people
managing the patches? In particular, what does the workflow l
Alex Kost skribis:
> Ricardo Wurmus (2016-03-23 10:41 +0300) wrote:
>
>> Chris Marusich writes:
>>
>>> While we're talking about patches, I'm curious: how are other people
>>> managing the patches? In particular, what does the workflow look like
>>> for people who are committing? Do you manual
On Tue, Mar 22, 2016 at 09:44:47PM -0700, Chris Marusich wrote:
>
> While we're talking about patches, I'm curious: how are other people
> managing the patches? In particular, what does the workflow look like
> for people who are committing? Do you manually download the patch (or
> patches) to a
On Wed 23 Mar 2016 09:15, Chris Marusich writes:
> Ricardo Wurmus writes:
>
>> I’m using an email client in Emacs, so the email as well as the attached
>> patch is shown in a regular text buffer. When I see the patch I can
>> directly apply it by running “git am” on the buffer contents, or by
>
Alex Kost writes:
>> I’m using an email client in Emacs, so the email as well as the attached
>> patch is shown in a regular text buffer. When I see the patch I can
>> directly apply it by running “git am” on the buffer contents, or by
>> opening a shell and running “git am” on the file associat
Ricardo Wurmus (2016-03-23 10:41 +0300) wrote:
> Chris Marusich writes:
>
>> While we're talking about patches, I'm curious: how are other people
>> managing the patches? In particular, what does the workflow look like
>> for people who are committing? Do you manually download the patch (or
>>
Ricardo Wurmus writes:
> I’m using an email client in Emacs, so the email as well as the attached
> patch is shown in a regular text buffer. When I see the patch I can
> directly apply it by running “git am” on the buffer contents, or by
> opening a shell and running “git am” on the file associa
Chris Marusich writes:
> While we're talking about patches, I'm curious: how are other people
> managing the patches? In particular, what does the workflow look like
> for people who are committing? Do you manually download the patch (or
> patches) to a temporary folder, view it/them, and if y
While we're talking about patches, I'm curious: how are other people
managing the patches? In particular, what does the workflow look like
for people who are committing? Do you manually download the patch (or
patches) to a temporary folder, view it/them, and if you like what you
see, commit it w
Nils Gillmann skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Hi!
>>
>> The best patch-tracking candidate I’ve seen so far is “patches”, written
>> by/for the QEMU people (the ‘patches’ package in Guix.)
>>
>> https://www.gnu.org/software/guix/packages/#patches
>>
>> I think it has every
l...@gnu.org (Ludovic Courtès) writes:
> Hi!
>
> The best patch-tracking candidate I’ve seen so far is “patches”, written
> by/for the QEMU people (the ‘patches’ package in Guix.)
>
> https://www.gnu.org/software/guix/packages/#patches
>
> I think it has everything most of us want, including an
Hi!
The best patch-tracking candidate I’ve seen so far is “patches”, written
by/for the QEMU people (the ‘patches’ package in Guix.)
https://www.gnu.org/software/guix/packages/#patches
I think it has everything most of us want, including an Emacs interface.
The main “difficulty” is setting it
Mathieu Lirzin writes:
> Cyril: Do you think the bot option is feasible?
Hi,
Nils Gillmann writes:
> As you maybe already noticed, and I hope this is not just a
> temporary impression I have after ~4 months or so, guix-devel is
> getting an increasing amount of messages per day and per month.
Same feeling here.
> In my opinion this makes it hard to keep track of pa
Nils Gillmann writes:
> Ricardo Wurmus writes:
>
>> Nils Gillmann writes:
>>
>>> First follow up idea:
>>>
>>> Ideal case would be:
>>> - integration with Guix in the future (the emacs interface and
>>>other potential future interfaces)
>>> - integration into Guix website
>>> - patches c
Ricardo Wurmus writes:
> Nils Gillmann writes:
>
>> First follow up idea:
>>
>> Ideal case would be:
>> - integration with Guix in the future (the emacs interface and
>>other potential future interfaces)
>> - integration into Guix website
>> - patches can be marked:
>>- state (done/op
Nils Gillmann writes:
> First follow up idea:
>
> Ideal case would be:
> - integration with Guix in the future (the emacs interface and
>other potential future interfaces)
> - integration into Guix website
> - patches can be marked:
>- state (done/open)
>- priority
> - patches ca
First follow up idea:
Ideal case would be:
- integration with Guix in the future (the emacs interface and
other potential future interfaces)
- integration into Guix website
- patches can be marked:
- state (done/open)
- priority
- patches can be assigned to more than 1 person
- webin
As you maybe already noticed, and I hope this is not just a
temporary impression I have after ~4 months or so, guix-devel is
getting an increasing amount of messages per day and per month.
In my opinion this makes it hard to keep track of patches and
maybe also makes the workflow of people with co
23 matches
Mail list logo
