Just wanted to follow up on a positive note and say "nice work on the new
release". It was an easy upgrade after I fixed my own issues.
On Monday, September 12, 2016 at 5:12:32 PM UTC-4, Tim Graham wrote:
> Correct, we never use git merge in Django. We always cherry-pick
> (backport) at the time of making the initial commit, but since we commit
> everything to master rather than a stable branch, our situation is a bit
> On Friday, September 9, 2016 at 8:24:52 AM UTC-4, Daniele Procida wrote:
>> On Thu, Sep 1, 2016, Tim Graham <timog...@gmail.com> wrote:
>> >admit that I don't really understand how git merging works but I find
>> >Django's cherry picking of commits to make backports to be very reliable
>> >terms of making history bisectable.
>> Hi Tim.
>> We're still trying to work out the right way to do this.
>> See <
>> As I understand, when a commit is cherry-picked into a different branch,
>> it acquires a different hash, so there is then no easy way to work out
>> whether the same code is in both branches (they don't share a commit
>> history that can be compared).
>> This makes it difficult to ensure that things are correctly ported
>> forward or backwards when required.
>> On the other hand, merging (which does preserve hashes/history) is an
>> all-or-nothing process, so not always suitable.
>> I'd love to know a way out of this dilemma.
Unsubscribe: send a message to
You received this message because you are subscribed to the Google Groups
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web, visit
For more options, visit https://groups.google.com/d/optout.