[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Managing patches and branches, retrospective and futher changes?
From: |
Christopher Baines |
Subject: |
Re: Managing patches and branches, retrospective and futher changes? |
Date: |
Mon, 29 Apr 2024 15:42:18 +0100 |
User-agent: |
mu4e 1.12.2; emacs 29.3 |
Andreas Enge <andreas@enge.fr> writes:
> Hello,
>
> Am Wed, Apr 24, 2024 at 02:21:56PM +0100 schrieb Christopher Baines:
>> Let me know if you have any thoughts or questions!
>
> in this part:
> +@item
> +Minimise the changes on master that are missing on the branch prior to
> +merging the branch in to master. Merging master in to the branch can be
> +appropriate for this purpose.
>
> I would drop the second sentence. It mildly contradicts the previous
> "avoid merging master into the branch". Writing "avoid merging" instead
> of "never merge" already allows for some leeway, I would prefer not to
> insist on it.
Yeah, maybe it's redundant. I think what I was trying to say is that
minimising the changes against master is a priority, so do this even if
you resort to merging master in to the branch.
signature.asc
Description: PGP signature
- Managing patches and branches, retrospective and futher changes?, Christopher Baines, 2024/04/24
- Re: Managing patches and branches, retrospective and futher changes?, Steve George, 2024/04/25
- Re: Managing patches and branches, retrospective and futher changes?, Efraim Flashner, 2024/04/26
- Re: Managing patches and branches, retrospective and futher changes?, Andreas Enge, 2024/04/29
- Re: Managing patches and branches, retrospective and futher changes?,
Christopher Baines <=