[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Merge Tracking Auditing - SoC

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: 2007-04-27 21:50:14 CEST

Hyrum K. Wright wrote:
> Mark Phippard wrote:
>> On 4/23/07, Hyrum K. Wright <hyrum_wright@mail.utexas.edu> wrote:
>>> Hyrum K. Wright wrote:
>>>> Hello all.
>>>> As many of you know, the approval for Summer of Code projects came last
>>>> week, and I've received funding to work on the auditing aspect of merge
>>>> tracking
>>> (http://subversion.tigris.org/merge-tracking/func-spec.html#commutative-author-and-rev).
>>>> I'm excited to get going on the project.
>>>> Over the next month, I'd like to finalize the functional spec at the
>>>> above URL. I would appreciate it if people could take a look at it and
>>>> suggest any changes. The pending questions in the spec, with varying
>>>> degrees of relevancy, are:
>>>> * How will --merge-sensitive behave for commits which remove merge info
>>>> (e.g. reverts)?
>>>> * In the case of svn log, would the user be better served if we just
>>>> included the original revision logs in line with the logs (i.e., no
>>>> special indentation, etc.)?
>>>> * What about svn ls --verbose, which also shows revisions and
>>> usernames?
>>> We've resolved these questions, but added one more:
>>> * What happens when svn status --show-updates has multiple original
>>> authors?
>> I think it should be handled the same as info and ls, which I believe
>> means no changes to current behavior.
> That sounds reasonable. If there are not dissenting opinions, I'll add
> it to the spec.

Done in r24817.


Received on Fri Apr 27 21:50:33 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.