Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
-
Re: ignoring formatting commits with new git feature
Thank you David for sharing this. Very useful to know!lmignonOn Thu, Jun 4, 2020 at 1:57 PM David Beal <david.beal@akretion.com> wrote:Hi all, As explained here https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame since git 2.23 it's easy to ignore some commits to keep git blame cmd also efficient than without these commits. Shortly: - add a .git-blame-ignore-revs in your repo and put commits to ignore (black ones mainly) - apply git config blame.ignoreRevsFile .git-blame-ignore-revs : now git blame works with the most informative way about authoring if you have git 2.23 at least I think it can be interesting to use OCA. What do you think ? Bonne journée David BEAL - akretion.com Chef de projet Odoo Développement / Intégration
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Laurent Mignon - 02:41 - 4 Jun 2020 -
Re: ignoring formatting commits with new git feature
Interesting, nevertheless what kind of commit do you want to bypass in git blame, if I get it correctly we could ignore the linting commits that way?Which could come handy with all modules we applied black on.Yannick VaucherBusiness Solutions ArchitectCamptocamp SAPSE A, CH-1015 LausannePhone: +41 21 619 10 30Office: +41 21 619 10 10On Thu, 4 Jun 2020 at 13:57, David Beal <david.beal@akretion.com> wrote:Hi all, As explained here https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame since git 2.23 it's easy to ignore some commits to keep git blame cmd also efficient than without these commits. Shortly: - add a .git-blame-ignore-revs in your repo and put commits to ignore (black ones mainly) - apply git config blame.ignoreRevsFile .git-blame-ignore-revs : now git blame works with the most informative way about authoring if you have git 2.23 at least I think it can be interesting to use OCA. What do you think ? Bonne journée David BEAL - akretion.com Chef de projet Odoo Développement / Intégration
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yannick Payot - 02:41 - 4 Jun 2020 -
Re: ignoring formatting commits with new git feature
Hi David,Yes this is very helpful. I glimpsed that existed but could not find it again until now.Thanks a lot for sharing!-sbiOn Thu, Jun 4, 2020 at 1:57 PM David Beal <david.beal@akretion.com> wrote:Hi all, As explained here https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame since git 2.23 it's easy to ignore some commits to keep git blame cmd also efficient than without these commits. Shortly: - add a .git-blame-ignore-revs in your repo and put commits to ignore (black ones mainly) - apply git config blame.ignoreRevsFile .git-blame-ignore-revs : now git blame works with the most informative way about authoring if you have git 2.23 at least I think it can be interesting to use OCA. What do you think ? Bonne journée David BEAL - akretion.com Chef de projet Odoo Développement / Intégration
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 02:36 - 4 Jun 2020 -
ignoring formatting commits with new git feature
Hi all, As explained here https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame since git 2.23 it's easy to ignore some commits to keep git blame cmd also efficient than without these commits. Shortly: - add a .git-blame-ignore-revs in your repo and put commits to ignore (black ones mainly) - apply git config blame.ignoreRevsFile .git-blame-ignore-revs : now git blame works with the most informative way about authoring if you have git 2.23 at least I think it can be interesting to use OCA. What do you think ? Bonne journée David BEAL - akretion.com Chef de projet Odoo Développement / Intégration
by David BEAL - 01:56 - 4 Jun 2020 -
Re: Info on "lost" PR
I like "make reviews to get reviewers", the domino effect can have a good result in this case.
My only problem is to learn (Odoo, code, ...) do to useful review, but I will do.ThanksStefanoDa: "Daniel Reis" dreis@opensourceintegrators.com
Hi Stefan, not a procedure, more like a social skill :-)I usually try tagging/pinging people to help, but that’s not always successful.Next you can look for other pending PRs and do review them. That “entitles” you to ask the person to review back your PR.This is not because of you or what you’re doing. It happens to me also. The thing is we have more PR proponents that PR reviewers. The solution, IMO, is to make reviews to get reviewers.ThanksDanielDa: "Stefano Consolaro" stefano.consolaro@mymage.it
Hi Daniel,
sorry if I write directly to you, but I need help to understand the right path to complete the PR.
Some time ago you approved one of my PR https://github.com/OCA/management-system/pull/265 (my first on OCA ;-)), but I have other that are waiting:
264, 266, 267, 282, 283, 284, 286 and the porting of 265: 325 and 326.There is some procedure to request revisions or your team do it based on community necessity/priority?Some hint?Thanks in advance
by Stefano Consolaro - 11:35 - 2 Jun 2020 -
Re: Info on "lost" PR
Hi Stefan, not a procedure, more like a social skill :-)I usually try tagging/pinging people to help, but that’s not always successful.Next you can look for other pending PRs and do review them. That “entitles” you to ask the person to review back your PR.This is not because of you or what you’re doing. It happens to me also. The thing is we have more PR proponents that PR reviewers. The solution, IMO, is to make reviews to get reviewers.ThanksDaniel--Stefano Consolaro <stefano.consolaro@mymage.it> escreveu em seg, 1/06/2020 às 23:33 :Well done, I used the list address :-(Remember to not do some things after midnight.
Da: "Stefano Consolaro" stefano.consolaro@mymage.itCc:Data: Tue, 2 Jun 2020 00:26:07 +0200Oggetto: Info on "lost" PR
Hi Daniel,
sorry if I write directly to you, but I need help to understand the right path to complete the PR.
Some time ago you approved one of my PR https://github.com/OCA/management-system/pull/265 (my first on OCA ;-)), but I have other that are waiting:
264, 266, 267, 282, 283, 284, 286 and the porting of 265: 325 and 326.There is some procedure to request revisions or your team do it based on community necessity/priority?Some hint?Thanks in advanceStefano ConsolaroStefano Consolaro_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Thanks
Daniel
by Daniel Reis - 12:45 - 2 Jun 2020 -
Re: Info on "lost" PR
Well done, I used the list address :-(Remember to not do some things after midnight.
Da: "Stefano Consolaro" stefano.consolaro@mymage.itA: contributors@odoo-community.orgCc:Data: Tue, 2 Jun 2020 00:26:07 +0200Oggetto: Info on "lost" PR
Hi Daniel,
sorry if I write directly to you, but I need help to understand the right path to complete the PR.
Some time ago you approved one of my PR https://github.com/OCA/management-system/pull/265 (my first on OCA ;-)), but I have other that are waiting:
264, 266, 267, 282, 283, 284, 286 and the porting of 265: 325 and 326.There is some procedure to request revisions or your team do it based on community necessity/priority?Some hint?Thanks in advanceStefano Consolarowww.mymage.itStefano Consolarowww.mymage.it
by Stefano Consolaro - 12:31 - 2 Jun 2020 -
Info on "lost" PR
Hi Daniel,
sorry if I write directly to you, but I need help to understand the right path to complete the PR.
Some time ago you approved one of my PR https://github.com/OCA/management-system/pull/265 (my first on OCA ;-)), but I have other that are waiting:
264, 266, 267, 282, 283, 284, 286 and the porting of 265: 325 and 326.There is some procedure to request revisions or your team do it based on community necessity/priority?Some hint?Thanks in advanceStefano Consolarowww.mymage.it
by Stefano Consolaro - 12:31 - 2 Jun 2020 -
Re: Add v 12.0 to Fleet
Perfet! Thank you Daniel!
Da: "Daniel Reis" dreis@opensourceintegrators.comA: "Contributors" contributors@odoo-community.orgCc:Data: Mon, 01 Jun 2020 13:31:55 -0000Oggetto: Re: Add v 12.0 to Fleet
Done!
On 31/05/2020 22:21, Stefano Consolaro wrote:
Hi,in https://github.com/OCA/fleet I see only v.13 branch.It is possible to have v.12 too?I have a micro module to propose.Thanks
Stefano Consolaro
Stefano Consolarowww.mymage.it
by Stefano Consolaro - 05:51 - 1 Jun 2020 -
Re: Add v 12.0 to Fleet
Done!
On 31/05/2020 22:21, Stefano Consolaro wrote:
Hi,in https://github.com/OCA/fleet I see only v.13 branch.It is possible to have v.12 too?I have a micro module to propose.Thanks
Stefano Consolaro
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Daniel Reis - 03:30 - 1 Jun 2020 -
Add v 12.0 to Fleet
Hi,in https://github.com/OCA/fleet I see only v.13 branch.It is possible to have v.12 too?I have a micro module to propose.ThanksStefano Consolarowww.mymage.it
by Stefano Consolaro - 11:20 - 31 May 2020 -
Re: OCA modules library mismatch.
Superb! Thanks Simone!On Thu, May 28, 2020 at 2:32 PM Simone Rubino <simone.rubino@agilebg.com> wrote:Hi, in italian localization we have solved a similar issue we had with `pyxb`'s version with this commit https://github.com/OCA/l10n-italy/commit/ff609d376743cfd85b2d9bb5b44c17381d2f5b9e.Hope it helps!On Thu, 28 May 2020 at 07:17, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:Dear community,While adding features into some https://github.com/OCA/l10n-thailand/ modules PR. We found that we need newer version of python lib than what is installed by odoo core.Core odoo used num2words v.0.5.6 (exclude th currency) but the module need num2words v.0.5.7. So our test will fail.How do we get away with this?Thank you_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 12:40 - 28 May 2020 -
Re: OCA modules library mismatch.
Hi, in italian localization we have solved a similar issue we had with `pyxb`'s version with this commit https://github.com/OCA/l10n-italy/commit/ff609d376743cfd85b2d9bb5b44c17381d2f5b9e.Hope it helps!On Thu, 28 May 2020 at 07:17, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:Dear community,While adding features into some https://github.com/OCA/l10n-thailand/ modules PR. We found that we need newer version of python lib than what is installed by odoo core.Core odoo used num2words v.0.5.6 (exclude th currency) but the module need num2words v.0.5.7. So our test will fail.How do we get away with this?Thank you_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Simone Rubino - 09:31 - 28 May 2020 -
OCA modules library mismatch.
Dear community,While adding features into some https://github.com/OCA/l10n-thailand/ modules PR. We found that we need newer version of python lib than what is installed by odoo core.Core odoo used num2words v.0.5.6 (exclude th currency) but the module need num2words v.0.5.7. So our test will fail.How do we get away with this?Thank you
by Kitti Upariphutthiphong - 07:16 - 28 May 2020 -
Re: New OpenUpgrade usage mailing list
Thanks!Le mer. 27 mai 2020 à 16:26, Ivan Todorovich <ivan.todorovich@druidoo.io> a écrit :Thanks Pedro!El mié., 27 may. 2020 a las 15:47, Sylvain LE GAL (<sylvain.legal@grap.coop>) escribió:Thanks Pedro !> As the usage of OpenUpgrade is increasingGood news !regards.Le mer. 27 mai 2020 à 13:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Hi, contributors!As the usage of OpenUpgrade is increasing and the issue tracker of the GitHub repository is not for asking questions about its usage and problems outside of the migration scripts themselves, we have created a new mailing list for handling all of this:You can subscribe to it at https://odoo-community.org/groups. For those not collaborating directly with the development of the migration scripts, but have experience using the tool for migrating databases, please subscribe and reply to newcomers that try to use it and ask here.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Joël Grand Guillaume - 09:26 - 27 May 2020 -
Re: New OpenUpgrade usage mailing list
Thanks Pedro!El mié., 27 may. 2020 a las 15:47, Sylvain LE GAL (<sylvain.legal@grap.coop>) escribió:Thanks Pedro !> As the usage of OpenUpgrade is increasingGood news !regards.Le mer. 27 mai 2020 à 13:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Hi, contributors!As the usage of OpenUpgrade is increasing and the issue tracker of the GitHub repository is not for asking questions about its usage and problems outside of the migration scripts themselves, we have created a new mailing list for handling all of this:You can subscribe to it at https://odoo-community.org/groups. For those not collaborating directly with the development of the migration scripts, but have experience using the tool for migrating databases, please subscribe and reply to newcomers that try to use it and ask here.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Iván Todorovich - 04:25 - 27 May 2020 -
Re: New OpenUpgrade usage mailing list
Thanks Pedro !> As the usage of OpenUpgrade is increasingGood news !regards.Le mer. 27 mai 2020 à 13:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Hi, contributors!As the usage of OpenUpgrade is increasing and the issue tracker of the GitHub repository is not for asking questions about its usage and problems outside of the migration scripts themselves, we have created a new mailing list for handling all of this:You can subscribe to it at https://odoo-community.org/groups. For those not collaborating directly with the development of the migration scripts, but have experience using the tool for migrating databases, please subscribe and reply to newcomers that try to use it and ask here.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sylvain LE GAL - 03:45 - 27 May 2020 -
New OpenUpgrade usage mailing list
Hi, contributors!As the usage of OpenUpgrade is increasing and the issue tracker of the GitHub repository is not for asking questions about its usage and problems outside of the migration scripts themselves, we have created a new mailing list for handling all of this:You can subscribe to it at https://odoo-community.org/groups. For those not collaborating directly with the development of the migration scripts, but have experience using the tool for migrating databases, please subscribe and reply to newcomers that try to use it and ask here.Regards.
by Pedro M. Baeza - 01:36 - 27 May 2020 -
Re: OCA DMS modules coming from MuK
Great! Thanks a lot to MuK and OCA contributors.On Wed, May 20, 2020 at 6:32 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:I'm glad to announce that MuK IT has agreed to move their great DMS modules to OCA, starting with the version 13.0. The repository has been already created and a first proposal has arisen from the Spanish OCA Days celebrated these past 2 days thanks to several contributors like Enric Tobella, Gelu Boros and Antoni Romera:You can review it for getting it merged and also start enjoying it. More extensions are to come in the future.Thanks to Mathias and Derrim from MuK for this move and the rest of the involved people.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40
by Alex Comba. - 09:25 - 21 May 2020 -
Re: OCA DMS modules coming from MuK
Cool! Thanks to MuK and OCA sprinters!On Wed, May 20, 2020 at 6:32 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:I'm glad to announce that MuK IT has agreed to move their great DMS modules to OCA, starting with the version 13.0. The repository has been already created and a first proposal has arisen from the Spanish OCA Days celebrated these past 2 days thanks to several contributors like Enric Tobella, Gelu Boros and Antoni Romera:You can review it for getting it merged and also start enjoying it. More extensions are to come in the future.Thanks to Mathias and Derrim from MuK for this move and the rest of the involved people.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Simone Orsi - 08:30 - 21 May 2020