Hello Vagrant,
sorry for the delay with this reply (maybe meanwhile someone else have
already done all or some of my considerations)
Vagrant Cascadian writes:
[...]
>> The point is that triaging is a (boring) activity that Someone™ should
>> perform, sooner or later (as Vagrant did with the
Hi Efraim,
Efraim Flashner writes:
[...]
> On the other hand, if we do manage to automate writing of commit
> messages, it makes one less thing for committers to manually fix before
> pushing the commit.
It would be lovely! It could also be done by a client-side git hook,
provided in the
Hi Maxim,
On Sat, 09 Sep 2023 at 19:50, Maxim Cournoyer wrote:
>>> --8<---cut here---start->8---
>>> random=$({ git var GIT_COMMITTER_IDENT ; echo "$refhash" ; cat "$1"; } |
>>> git hash-object --stdin)
>>> --8<---cut
Hi Liliana,
On Sun, 10 Sep 2023 at 00:20, Liliana Marie Prikler
wrote:
>> > > Must we force a single workflow on everyone, even if our track
>> > > record in reviewing and merging doesn’t clearly show that our way
>> > > is superior
>> >
>> > Again, define superior.
>>
>> No, I won’t. I
Hi Maxim,
Maxim Cournoyer writes:
[...]
>> c. how do we get the issue number of a patch containing "Change-Id"? [1]
>
> We'd have to search through the currently opened patches issues; I
> assume using a tool like the 'mumi' command we already have could do
> that.
It would be fantastic if we
Hi Maxim,
For reference [1].
On Sat, 09 Sep 2023 at 18:14, Maxim Cournoyer wrote:
> On a related note sometimes we have WIP kind of work that stays on our
> tracker with deeper questions / problems to solve, and I don't think
> it's fair for our reviewers to have these linger on for years on
Hi!
Liliana Marie Prikler writes:
> Am Donnerstag, dem 07.09.2023 um 09:12 -0700 schrieb Vagrant Cascadian:
>> I am much more comfortable with the "Fixes" convention of:
>>
>> Fixes: https://issues.guix.gnu.org/NNN
OK, I understand Vagrant's concerns: we need a _namespaced_ URI, but
there
Hello,
(I find it difficult to efficiently follow this thread and to keep up to
date with reading it, so please forgive me if someone else already
addressed my considerations)
Simon Tournier writes:
[...]
> « For which contributors do we want to/can we decrease the cognitive
> overhead? », so
Hi Giovanni,
Giovanni Biscuolo writes:
> Hi Maxim,
>
> Maxim Cournoyer writes:
>
> [...]
>
>>> c. how do we get the issue number of a patch containing "Change-Id"? [1]
>>
>> We'd have to search through the currently opened patches issues; I
>> assume using a tool like the 'mumi' command we
Hi,
Simon Tournier writes:
> Hi Maxim,
>
> Thanks for the explanations.
>
> On Mon, 11 Sept 2023 at 15:47, Maxim Cournoyer
> wrote:
>
>> > 2. How is Change-Id linked to #65280?
>>
>> Each patch submission ("issue") can have one or multiple commits. We'd
>> know for sure the series was merged
Hi Simon,
Simon Tournier writes:
> Hi Maxim,
>
> On Sat, 09 Sep 2023 at 19:50, Maxim Cournoyer
> wrote:
>
--8<---cut here---start->8---
random=$({ git var GIT_COMMITTER_IDENT ; echo "$refhash" ; cat "$1"; } |
git hash-object --stdin)
Hi Liliana,
Liliana Marie Prikler writes:
[...]
> For example, whenever people say that "forges would improve stuff", my
> reply is (modulo phrasing) "yes, for the people who are already used to
> forges".
I just want to point out that actually Guix _do_have_ a forge. the
software is Savane
Hi Maxim,
Thanks for the explanations.
On Mon, 11 Sept 2023 at 15:47, Maxim Cournoyer
wrote:
> > 2. How is Change-Id linked to #65280?
>
> Each patch submission ("issue") can have one or multiple commits. We'd
> know for sure the series was merged (and thus can be closed) when the
> set of
Hi Giovanni,
Giovanni Biscuolo writes:
> Hi!
>
> Liliana Marie Prikler writes:
>
>> Am Donnerstag, dem 07.09.2023 um 09:12 -0700 schrieb Vagrant Cascadian:
>>> I am much more comfortable with the "Fixes" convention of:
>>>
>>> Fixes: https://issues.guix.gnu.org/NNN
>
> OK, I understand
Hi Simon,
Am Montag, dem 11.09.2023 um 12:36 +0200 schrieb Simon Tournier:
> Today, the review and commit process have many steps, more or less
> simple, not all sure!, well at the end, we have something complex.
>
> One trivial step is to apply the patch (or series) to your local
> checkout and
On 2023-09-11 17:17:24 +0200, Simon Tournier wrote:
> Hi,
>
> On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès wrote:
>
> > Note that the patch series adds a hard dependency on Git.
> > This is because the existing ‘git-fetch’ code depends on Git,
> > which is itself motivated by the fact that Git
Am Montag, dem 11.09.2023 um 10:09 +0200 schrieb Giovanni Biscuolo:
> Hi!
>
> Liliana Marie Prikler writes:
>
> > Am Donnerstag, dem 07.09.2023 um 09:12 -0700 schrieb Vagrant
> > Cascadian:
> > > I am much more comfortable with the "Fixes" convention of:
> > >
> > > Fixes:
Hi Simon,
Simon Tournier writes:
> Hi Maxim,
>
> For reference [1].
>
> On Sat, 09 Sep 2023 at 18:14, Maxim Cournoyer
> wrote:
>
>> On a related note sometimes we have WIP kind of work that stays on our
>> tracker with deeper questions / problems to solve, and I don't think
>> it's fair for
Hi,
Liliana Marie Prikler writes:
[...]
> Maybe make that bug-guix so that it matches with the mailing list name,
> though we also need a wording for when a patch is not a bug, e.g. a
> simple package upgrade.
>
> WDYT about the following
> Applies: [patch]
> Closes: [patch]
>
Hi Maxim,
Maxim Cournoyer writes:
[...]
>> If there is enough consensus I volunteer to collect ideas and send a
>> feature request to the mumi and/or Debbugs devels (if we need Debbugs
>> patches I guess it will be a long term goal)
>
> I don't think any changes to Debbugs would be necessary.
Re,
On Mon, 11 Sep 2023 at 17:17, Simon Tournier wrote:
> On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès wrote:
>
>> Note that the patch series adds a hard dependency on Git.
>> This is because the existing ‘git-fetch’ code depends on Git,
>> which is itself motivated by the fact that Git
Hi,
Simon Tournier writes:
> Hi,
>
> On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès wrote:
>
>> Note that the patch series adds a hard dependency on Git.
>> This is because the existing ‘git-fetch’ code depends on Git,
>> which is itself motivated by the fact that Git supports
>> shallow clones
Hi wolf,
wolf writes:
[...]
>> Personally, I do not have a strong opinion about the Big Plan™. I note
>> that the introduction of Git as a hard dependency is a slippery slope
>> considering the current state of libgit2. Here, it starts with “git
>> clone”, then “git gc” (unsupported by
Hi Guix developers,
I'm hosting a panel for the University of California Santa Cruz's Open
Source symposium.
The panel will be on "Reproducibility" ---
My goal is to try and get representatives from Guix, Spack & Nix to
talk about various aspects of the store-model, reproducibility
challenges
Hi,
On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès wrote:
> Note that the patch series adds a hard dependency on Git.
> This is because the existing ‘git-fetch’ code depends on Git,
> which is itself motivated by the fact that Git supports
> shallow clones and libgit2/Guile-Git doesn’t.
Going
Hi,
On Mon, 11 Sep 2023 at 09:37, Giovanni Biscuolo wrote:
> A more useful mumi (web or CLI) query to search for duplicates would be:
>
> is:open tag:patch subject:
[...]
> is enough, but (is:open and tag:patch,moreinfo) is better:
>
>
Hi Mathieu,
On Sun, 10 Sep 2023 at 11:14, Mathieu Othacehe wrote:
> Here is a status of cross-compilation in Guix. For cross-compilation to
> work, the build-system needs to support cross-compilation.
>
> The following build-systems explicitly refuse cross-compiling packages:
>
> haskell, agda,
Hi Simon
Simon Tournier writes:
[...]
>> is enough, but (is:open and tag:patch,moreinfo) is better:
[...]
>> We could also add a feature to have "saved searches" in mumi web and CLI
>> interfaces to help with this task.
>
> Well, the Mumi CLI, “guix shell mumi” and then “mumi search”, should
Am Montag, dem 11.09.2023 um 18:19 +0200 schrieb Simon Tournier:
> Hi Mathieu,
>
> On Sun, 10 Sep 2023 at 11:14, Mathieu Othacehe
> wrote:
>
> > Here is a status of cross-compilation in Guix. For cross-
> > compilation to
> > work, the build-system needs to support cross-compilation.
> >
> >
Hi Liliana,
Liliana Marie Prikler writes:
> Am Montag, dem 11.09.2023 um 14:36 -0400 schrieb Maxim Cournoyer:
>> Hi,
>>
>> Liliana Marie Prikler writes:
>>
>> [...]
>>
>> > Maybe make that bug-guix so that it matches with the mailing list
>> > name,
>> > though we also need a wording for when
Hi Maxim,
On Mon, 11 Sep 2023 at 13:54, Maxim Cournoyer wrote:
> If you want to package elasticsearch, know it's not in the Guix as we
> speak, and see it as the first item when browsing
> https://issues.guix.gnu.org/search?query=elasticsearch, I have some hope
> that someone could find it.
Hi Liliana,
On Mon, 11 Sep 2023 at 19:53, Liliana Marie Prikler
wrote:
> For "patch does not apply", the forge solution is typically to send a
> notification to the issuer.
No, that does not match my small experience. Because often the issuer
is gone or not responding. As a reviewer using
Am Montag, dem 11.09.2023 um 14:36 -0400 schrieb Maxim Cournoyer:
> Hi,
>
> Liliana Marie Prikler writes:
>
> [...]
>
> > Maybe make that bug-guix so that it matches with the mailing list
> > name,
> > though we also need a wording for when a patch is not a bug, e.g. a
> > simple package
On 2023-09-11, Simon Tournier wrote:
> On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès wrote:
>> Note that the patch series adds a hard dependency on Git.
>> This is because the existing ‘git-fetch’ code depends on Git,
>> which is itself motivated by the fact that Git supports
>> shallow clones
Vagrant Cascadian writes:
> [[PGP Signed Part:Undecided]]
> On 2023-09-11, Simon Tournier wrote:
>> On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès wrote:
>>> Note that the patch series adds a hard dependency on Git.
>>> This is because the existing ‘git-fetch’ code depends on Git,
>>> which is
Giovanni Biscuolo writes:
> [[PGP Signed Part:Undecided]]
> Hi Liliana,
>
> Liliana Marie Prikler writes:
>
> [...]
>
>> For example, whenever people say that "forges would improve stuff", my
>> reply is (modulo phrasing) "yes, for the people who are already used to
>> forges".
>
> I just
Hi Simon,
Simon Tournier writes:
> Hi Maxim,
>
> On Mon, 11 Sep 2023 at 13:54, Maxim Cournoyer
> wrote:
>
>> If you want to package elasticsearch, know it's not in the Guix as we
>> speak, and see it as the first item when browsing
>> https://issues.guix.gnu.org/search?query=elasticsearch, I
Hi Guix!
The end of August Astronomy related packages udpates and new packages.
Hope QA will green them
up soon :)
* Updates
- date-time :: 20230905T163102+0100
- commit :: 8d19ff23052bffb1c43f0d39f543eb0b1e363074
- issues :: https://issues.guix.gnu.org/65814
- quick [16/16][100%]
- [X]
Hi,
On Mon, 11 Sep 2023 at 14:26, Maxim Cournoyer wrote:
> In the grand scheme of things (pun intended), we'd like every
> programming to be feasible via nice Scheme APIs, which is what Guile-Git
> provides to work with git repositories. The appeal is to have a single
> language to rule them
39 matches
Mail list logo
