On Fri, Sep 17, 2010 at 2:50 PM, <saulgo...@flashingtwelve.brickfilms.com>wrote:

> Quoting Richard Hipp <d...@sqlite.org>:
>
> > Thank you for taking on this task - my plate is full at the moment.
> >
> > Please see my edits below
>
> Thanks to both you and zachtodd for your feedback.
>
> I have changed answer to the 'annotate' question to "Partial" because
> Fossil's annotation seems to show the first commit in which the line
> was added, as opposed to the "last modified" criteria posed in the
> comparison's question (the question also implied that a full history
> of the line should be provided). If it is thought that first commit
> information is as useful as the last modified, I would change the
> "Partial" to something that reflects that view. Or perhaps there is an
> option to show the most recent? Or a way to track from the first
> commit down to the most recent?
>

It should be showing the last modification.  If it isn't that's a bug.
Please report the bug.


>
> I have updated the text as follows (I am only showing the questions
> whose answers have been changed).
>
> Regards.
>
> =====================================
> > Atomic Commits
> >
> > Support for atomic commits means that if an
> > operation on the repository is interrupted
> > in the middle, the repository will not be
> > left in an inconsistent state. Are the
> > check-in operations atomic, or can
> > interrupting an operation leave the
> > repository in an intermediate state?
>
> Yes. Commits are atomic.
>
> > Intelligent Merging after Moves or Renames
> >
> > If the system keeps tracks of renames, does it support
> > intelligent merging of the files in the history after
> > the rename? (For example, changing a file in a renamed
> > directory, and trying to merge it).
>
> No, renames are not intelligent (feature is on the TODO list).
>
> > Tracking Line-wise File History
> >
> > Does the version control system have an option to track the
> > history of the file line-by-line? I.e., can it show for each
> > line at which revision it was most recently changed, and by
> > whom?
>
> Partial. Line-by-line history shows at which revision the line
> was introduced.
>
> > Tracking Uncommited Changes
> >
> > Does the software have an ability to track the changes in the
> > working copy that were not yet committed to the repository?
>
> Yes. Using 'fossil diff' or 'fossil gdiff'. Tracking status of
> all files is also available.
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>



-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to