New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MOLS for n=18,57,154,276,298,342 #16356
Comments
Dependencies: #16295 |
Branch: u/ncohen/16356 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
Reviewer: Vincent Delecroix |
comment:4
Hi Nathann, this is an easy one... Vincent |
comment:5
Yo !
Ahahah. I just added #16430 which does a couple of trivial things too... Nathann |
Changed branch from u/ncohen/16356 to |
Changed commit from |
comment:7
Volker I'm sorry but this ticket has an unreviewed dependency..... Nathann |
comment:8
(and I never meant to remove the commit) |
comment:9
(and apparently I cannot set it back, filling the form changes nothing) |
Commit: |
Changed branch from |
comment:12
Please don't set tickets to positive review that you don't want merged |
comment:14
Replying to @nathanncohen:
This is my mistake. I am very sorry. |
comment:15
Ok. I rebased on the new #16295 at public/16295. Please Nathann have a quick look. |
comment:16
What did you rebase ? For me public/16295 is equal to u/ncohen16295. Nathann |
comment:17
My mistake... it is not anymore. The git rebase does not move the current branch to another position. |
comment:18
Still the same for me. BTW don't use "rebase" (it rewrites the history) but merge ! Nathann |
comment:19
Replying to @nathanncohen:
It is not. If you fetch public/16356 the last commit is 7475474b531df3ef96d218e93045d24d254cff3c being different from the one here. So the rebase just worked. |
comment:20
Why on earth would you rebase the whole branch ? It will make all commits incompatible ! Nathann |
comment:21
Actually it is just the rebase of one commit. You prefer to have a merge and keep this commit unchanged ? |
comment:22
.... If you rebase this commit, then all patches above have to be updated. And basically all design branches in Anyway there is no need to merge this branch with the updated #16295, because there are no merge conflicts. And the tests pass. Nathann |
comment:23
All right! |
comment:24
Thanks ! Nathann (please set your name as Reviewer) |
comment:25
Replying to @nathanncohen:
Already done (see comment:4) |
comment:26
Oops, right |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
Changed branch from u/ncohen/16356 to |
As usual, those were given by Julian R. Abel.
Whose mind is filled with combinatorial designs.
Nathann
Depends on #16295
CC: @videlec @KPanComputes @dimpase @brettpim
Component: combinatorial designs
Author: Nathann Cohen
Branch/Commit:
917dd5c
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/16356
The text was updated successfully, but these errors were encountered: