Christopher Baines writes:
> I've spent a bunch of time in the last few days trying to see if I can
> get the bordeaux build farm moving on core-updates and I think things
> are moving at pace now.
Following on from this, builds have mostly paused for the last few days
as many changes have
Hi Christopher,
Christopher Baines writes:
> Maxim Cournoyer writes:
>
>> Guillaume Le Vaillant writes:
>>
>>> Lars-Dominik Braun skribis:
>>>
Hi,
it seems the core-updates branch is first in the merge-queue. haskell-team
was successfully built by the CI and is ready to
Hey,
I've spent a bunch of time in the last few days trying to see if I can
get the bordeaux build farm moving on core-updates and I think things
are moving at pace now.
Builds are happening for 6 systems, with the only major omission being
i586-gnu, I think there are existing issues with the
Maxim Cournoyer writes:
> Guillaume Le Vaillant writes:
>
>> Lars-Dominik Braun skribis:
>>
>>> Hi,
>>>
>>> it seems the core-updates branch is first in the merge-queue. haskell-team
>>> was successfully built by the CI and is ready to be merged. Since there
>>> does not seem to be an ETA for
Hi,
Guillaume Le Vaillant writes:
> Maxim Cournoyer skribis:
>
>> Hi,
>>
>> Guillaume Le Vaillant writes:
>>
>>> Lars-Dominik Braun skribis:
>>>
Hi,
it seems the core-updates branch is first in the merge-queue. haskell-team
was successfully built by the CI and is ready to
Maxim Cournoyer skribis:
> Hi,
>
> Guillaume Le Vaillant writes:
>
>> Lars-Dominik Braun skribis:
>>
>>> Hi,
>>>
>>> it seems the core-updates branch is first in the merge-queue. haskell-team
>>> was successfully built by the CI and is ready to be merged. Since there
>>> does not seem to be an
Hi,
Guillaume Le Vaillant writes:
> Lars-Dominik Braun skribis:
>
>> Hi,
>>
>> it seems the core-updates branch is first in the merge-queue. haskell-team
>> was successfully built by the CI and is ready to be merged. Since there
>> does not seem to be an ETA for core-updates, can I skip the
Lars-Dominik Braun skribis:
> Hi,
>
> it seems the core-updates branch is first in the merge-queue. haskell-team
> was successfully built by the CI and is ready to be merged. Since there
> does not seem to be an ETA for core-updates, can I skip the queue and
> go ahead with merging haskell-team?
Hi,
it seems the core-updates branch is first in the merge-queue. haskell-team
was successfully built by the CI and is ready to be merged. Since there
does not seem to be an ETA for core-updates, can I skip the queue and
go ahead with merging haskell-team?
Lars
Hi Chris and all,
Christopher Baines skribis:
> I think keeping the Git commit history clean and representative is
> really important, so to me at least this means core-updates can't be
> merged to master in it's current form, even if the changes overall from
> these 6351 commits are
emacs has a script gitmerge.el, it can skip some commit when merge with
different merge rule (ours), maybe can make life easier:
https://git.savannah.gnu.org/cgit/emacs.git/tree/admin/gitmerge.el
https://git.savannah.gnu.org/cgit/emacs.git/tree/admin/notes/git-workflow
--
Hi Christopher,
Christopher Baines writes:
[...]
> Assuming we merge core-updates without doing anything about these
> duplicate commits, and taking the cwltool package as a semi-random
> example, if you do:
>
> git log -p gnu/packages/bioinformatics.scm
I trust the 'newest' (appearing
Maxim Cournoyer writes:
> Hi,
>
> Christopher Baines writes:
>
>> Christopher Baines writes:
>>
>>> I'm also really confused by what commits appear to be on the branch,
>>> take 12b15585a75062f3fba09d82861c6fae9a7743b2 which appears to be one
>>> core-updates, but it's a duplicate of
>>>
Let's see where we are with the branch currently.
Thanks,
Steve / Futurile
Hi,
Christopher Baines writes:
> Christopher Baines writes:
>
>> I'm also really confused by what commits appear to be on the branch,
>> take 12b15585a75062f3fba09d82861c6fae9a7743b2 which appears to be one
>> core-updates, but it's a duplicate of
>> e2a7c227dea5b361e2ebdbba24b923d1922a79d0
Christopher Baines writes:
> I'm also really confused by what commits appear to be on the branch,
> take 12b15585a75062f3fba09d82861c6fae9a7743b2 which appears to be one
> core-updates, but it's a duplicate of
> e2a7c227dea5b361e2ebdbba24b923d1922a79d0 which was pushed to
> master. Same with
Hey,
Thanks for raising this issue Steve, given the branch has been going for
around 9 months (since [1]) now, I think it's well overdue to start
looking at building and merging it.
1: https://lists.gnu.org/archive/html/guix-commits/2023-07/msg00332.html
I pushed a single commit plus a merge
17 matches
Mail list logo
