[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new release?
From: |
Ralph Corderoy |
Subject: |
Re: new release? |
Date: |
Thu, 21 Apr 2022 07:42:12 +0100 |
Hi Eric,
> I've pushed f188de902b613110d5943210f212adb680a2b44a to master
> now, which should resolve this test failure.
Thanks, but could you, and any other committers, try to use Git's
rebase rather than merge as it preserves your commits and their messages
rather than ‘Merge commit 'f188de902b613110d5943210f212adb680a2b44a'’
which doesn't spell out the fix for those browsing the commit log.
‘git pull --rebase’ does it, and that option can be made the default.
As well as git-pull(1), there's an explanation in
https://git-scm.com/book/en/v2/Git-Branching-Rebasing
--
Cheers, Ralph.
- Re: new release?, (continued)
- Re: new release?, David Levine, 2022/04/20
- Re: new release?, Ken Hornstein, 2022/04/20
- Re: new release?, David Levine, 2022/04/20
- Re: new release?, David Levine, 2022/04/23
- Re: new release?, Jay Vosburgh, 2022/04/21
- Re: new release?, Ralph Corderoy, 2022/04/21
- Re: new release?, Alexander Zangerl, 2022/04/20
- Re: new release?, Eric Gillespie, 2022/04/20
- Re: new release?,
Ralph Corderoy <=
- Re: new release?, David Levine, 2022/04/20
- Re: new release?, Alexander Zangerl, 2022/04/20
- Re: new release?, Simon Burge, 2022/04/20
- Re: new release?, David Levine, 2022/04/20
- Re: new release?, Simon Burge, 2022/04/20
- Re: new release?, David Levine, 2022/04/22
- Message not available
- Re: new release?, David Levine, 2022/04/20
Re: new release?, Ralph Corderoy, 2022/04/20