[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[be] [bug #22950] Merging and Comparing projects work opposite
From: |
Teus Benschop |
Subject: |
[be] [bug #22950] Merging and Comparing projects work opposite |
Date: |
Wed, 23 Apr 2008 03:28:28 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7 |
Update of bug #22950 (project bibledit):
Status: None => Confirmed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Yes, they do work in the opposite direction.
Comparing P1 with P2. P1 is viewed as the newest version, and P2 as the older
version.
Merging P1 (master) with P2 (edited), in this case P2 is the newest version,
as it is the "edited" project. Because it is now "edited" by the team, it is
newer, and it must be merged into the "master" copy. The master copy is always
older because it receives updates from the edited project.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?22950>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/