On 6/4/19 8:42 AM, schoone...@gmail.com wrote:
On 04/06/19 13:05, emc-developers-requ...@lists.sourceforge.net wrote:
Date: Mon, 3 Jun 2019 14:45:28 -0500
From: John Thornton
To: EMC developers
Subject: [Emc-developers] Merge Just One Commit Up
Message-ID:<21236f20-9c1c-944e-ab39-bed182
: Mon, 3 Jun 2019 14:45:28 -0500
From: John Thornton
To: EMC developers
Subject: [Emc-developers] Merge Just One Commit Up
Message-ID:<21236f20-9c1c-944e-ab39-bed182e41...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
How do you merge just your special commit from 2.7 to
On 04/06/19 13:05, emc-developers-requ...@lists.sourceforge.net wrote:
Date: Mon, 3 Jun 2019 14:45:28 -0500
From: John Thornton
To: EMC developers
Subject: [Emc-developers] Merge Just One Commit Up
Message-ID:<21236f20-9c1c-944e-ab39-bed182e41...@gmail.com>
Content-Type: text/plain; c
On Tue, 4 Jun 2019 at 07:03, Sebastian Kuzminsky
wrote:
>
> There's not really any way to merge just one commit. You merge the tip
> of one branch into the tip of another branch. This is the normal
> workflow, and it's good.
if there is something that absolutely shouldn't transfer from 2.7 to
On 6/3/19 1:45 PM, John Thornton wrote:
How do you merge just your special commit from 2.7 to 2.8 to master?
I use git, git-gui, and gitkraken.
There's not really any way to merge just one commit. You merge the tip
of one branch into the tip of another branch. This is the normal
workflow,
How do you merge just your special commit from 2.7 to 2.8 to master?
I use git, git-gui, and gitkraken.
Thanks
JT
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers