[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSoC 2020: Unexpected "regressions"...
From: |
Werner LEMBERG |
Subject: |
Re: GSoC 2020: Unexpected "regressions"... |
Date: |
Sun, 30 Aug 2020 05:31:35 +0200 (CEST) |
> I meant re-committing my first commit with the fix, then rebasing
> the dev/lamb/GSoC-2020-final branch on top of it to keep my history
> pretty.
In general, this is the ideal solution, since it cleans up your
branch. However, ...
> Would you rather I just made a new commit?
... if tweaking is too complicated inspite of the support given by
git, a simple add-on commit is just fine. Note that the GSoC deadline
means a freeze to your branch; for ongoing work you should then copy
your branch to another one and use this for further work (patches,
rebasing, etc.)
Werner
- GSoC 2020: Unexpected "regressions"..., Owen Lamb, 2020/08/28
- Re: GSoC 2020: Unexpected "regressions"..., Michael Käppler, 2020/08/28
- Re: GSoC 2020: Unexpected "regressions"..., Michael Käppler, 2020/08/28
- Re: GSoC 2020: Unexpected "regressions"..., Owen Lamb, 2020/08/29
- Re: GSoC 2020: Unexpected "regressions"..., Werner LEMBERG, 2020/08/29
- Re: GSoC 2020: Unexpected "regressions"..., Owen Lamb, 2020/08/29
- Re: GSoC 2020: Unexpected "regressions"..., Carl Sorensen, 2020/08/29
- Re: GSoC 2020: Unexpected "regressions"..., Owen Lamb, 2020/08/29
- Re: GSoC 2020: Unexpected "regressions"...,
Werner LEMBERG <=
Re: GSoC 2020: Unexpected "regressions"..., Han-Wen Nienhuys, 2020/08/28