ChangeLog - branch control and synchronization

Earnie Boyd <[email protected]>
Newsgroups gmane.comp.gnu.mingw.devel
Message-ID <CA+sc5m=UHQJeuBoXuW6bQD=vfGKxe07_OJcuZZsqi2OiDYdKWg@mail.gmail.com>
I have a branch 4.0-dev which has plenty of changes in 2012 and 2013.

I have branch 4.1-dev which has a few changes from 2012.

In a clone of the repository, I created to test merges, there was a
conflict in the ChangeLog.  That conflict pointed out the differences
in 4.1-dev.  So I decided to create a preamble of

RELEASE 4.0: and RELEASE 4.1: marking in the ChangeLog which release
the changes belong to but that puts the dates out-of-sequence.  Is
this acceptable or should I modify the dates for the 4.1 changes
making the date not realistic to the commit?

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.