Comment 7 for bug 213032
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 213032] Re: allow to change author (name <e-mail>) and description in past commits | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Fri, 2008-08-22 at 03:35 +0000, Daniel Watkins wrote:
> On Thu, 21 Aug 2008 11:51:15 -0000
> Steve <email address hidden> wrote:
> > I really don't understand why this would complicate the model?
> > There's a change in metadata, which gets transported the moment,
> > where an update / pull / merge happens.
> When I pull or merge from a branch, how do I determine which of the
> target and source branches metadata is more valid?
Conceptually you have a timeline for each commit message. So you have a
timeline for the commit message of revision uuid XYZ. If we tie those
timelines to the timeline of a branch, then any lookup of a revision
will require a branch as starting point to determine the timeline we
used for its commit message. Alternatively if we manage each timeline
separately (e.g. by having a journal of metadata edits) we could advance
that journal, and when reading a particular revision if there are
multiple unresolved edits to the commit message inform the client and
let them choose.
In other words, this is doable, but it's significantly complex - we
should really document use cases and start broad outlines of what we
want/need using our in-tree documentation approach. Its too big for a
bug.
-Rob
--
GPG key available at: <http://