On Fri, 26 Feb 2016 23:38:38 +1100,
David <bouncingc...@gmail.com> wrote:
> On 24 February 2016 at 10:05, Seb <splu...@gmail.com> wrote:
>> On Tue, 23 Feb 2016 23:57:06 +0100,
>> Moritz Neeb <li...@moritzneeb.de> wrote:
>> [...]
>>>> OK, I'v
exactly are the loose commits causing trouble?
Sure enough, these dangling commits were removed automatically without
any intervention. All is good.
Thanks!
--
Seb
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sun, 21 Feb 2016 03:12:49 +0100,
Moritz Neeb <li...@moritzneeb.de> wrote:
> Hi Seb,
> On 02/20/2016 11:58 PM, Seb wrote:
>> Hello,
>> I've recently learnt how to consolidate and clean up the master
>> branch's commit history. I've squashed/fixuped many c
gt; (as your problem description implies). You'd see the same behavior if
> you'd rebased D and E in "master" to become D' and E'. "topic" would
> still have old D and E in its history, and not D' and E'.
Thank you for this excellent explanation. I will look into
On Sun, 21 Feb 2016 03:12:49 +0100,
Moritz Neeb <li...@moritzneeb.de> wrote:
> Hi Seb,
> On 02/20/2016 11:58 PM, Seb wrote:
>> Hello,
>> I've recently learnt how to consolidate and clean up the master
>> branch's commit history. I've squashed/fixuped many c
to the
child branch still shows the non-rebased (dirty) commit history from
master. Am I misunderstanding something with this?
Thanks,
--
Seb
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
6 matches
Mail list logo
