Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14495
| From | Nicolas Chauvat <nicolas.chauvat@logilab.fr> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Enabling salsa-ci on all Debian Python Team repos |
| Date | 2022-09-23 09:00 +0200 |
| Message-ID | <F8KPg-9sPK-3@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <F7KHE-8QJj-3@gated-at.bofh.it> <F7Mgp-8RKR-1@gated-at.bofh.it> <F7NvP-8Sov-1@gated-at.bofh.it> <F84Gl-92Xi-3@gated-at.bofh.it> <F8J6N-9s10-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Carsten, Hi List, Le Fri, Sep 23, 2022 at 07:01:05AM +0200, Carsten Schoenert a écrit : > heavily force pushing to not blow up the git tree with dozens of Fixup > commits! In the 'official' git tree this is a no go of course. Would doing the work in a git branch and 'git merge --squash' at the end be a solution to this problem ? I have the same issue when trying to use CI to run tests instead of running them locally, but using Mercurial, I just 'hg amend' them and I end up with a clean history. <shamelessplug> With Mercurial and its concept of obsolete commit combined with the evolve extension, a team can amend commits and share these amended commits without anyone losing work. I never found the equivalent in git where rewriting an history to clean it once the dust as settled breaks every repository that already pulled these commits. In other words, Mercurial allows you to work in a decentralized fashion both on your source and on the history of your source. </shamelessplug> -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-19 12:50 +0200
Re: [Debian-salsa-ci] Enabling salsa-ci on all Debian Python Team repos Iñaki Malerba <ina@malerba.space> - 2022-09-19 14:20 +0200
Re: [Debian-salsa-ci] Enabling salsa-ci on all Debian Python Team repos Julian Gilbey <julian@d-and-j.net> - 2022-09-19 17:10 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Louis-Philippe Véronneau <pollo@debian.org> - 2022-09-19 19:20 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-19 20:20 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-20 10:40 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-20 14:40 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-20 16:20 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-20 17:40 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-20 21:20 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-21 12:20 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Brian May <brian@linuxpenguins.xyz> - 2022-09-23 01:10 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-21 12:00 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Samuel Thibault <sthibault@debian.org> - 2022-09-21 12:40 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-23 04:40 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-23 07:10 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Stefano Rivera <stefanor@debian.org> - 2022-09-23 08:30 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Nicolas Chauvat <nicolas.chauvat@logilab.fr> - 2022-09-23 09:00 +0200
Re: Enabling salsa-ci on all Debian Python Team repos Arnaud Ferraris <aferraris@debian.org> - 2022-09-21 13:20 +0200
csiph-web