What about branch "tk-diff-viewer? It would be nice to have a more
powerful diff --tk

RR

2015-01-16 9:31 GMT+01:00 Jan Nijtmans <jan.nijtm...@gmail.com>:
> 2015-01-15 21:49 GMT+01:00 Andy Bradford <amb-fos...@bradfords.org>:
>> I just looked at the changes.wiki and there is still the following:
>>
>>     Let  fossil new  no longer  create  an initial  empty commit  by
>>     default. The first commit after checking out an empty repository
>>     will become the initial commit.  (NOT PLANNED FOR 1.30, BUT DONE
>>     TO EXPOSE fossil new --empty TO MORE FIELD TESTING BEFORE MAKING
>>     ANY DECISION ON IT!)
>>
>> Does this need to be updated before 1.30 is made?
>
> Yes, this needs to be updated. Assuming this change is accepted
> for 1.30, I just removed the additional comment.
>
> Since chiselapp sometimes generates an additional "initial commit",
> this change would be a perfect solution for the problem
> discussed here:
>      
> <http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/18273>
>
> But I'm open for any reason why this would be a bad idea. All
> corner-cases have been fixed now, the last one was reported
> by Michai Ramakers in July:
>     
> <http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/17266>
>
> So, this feature is already tested for almost half a year with success by
> many users ;-)
>
> Thanks, Andy, for the reminder!
>
> Regards,
>          Jan Nijtmans
> _______________________________________________
> fossil-dev mailing list
> fossil-dev@lists.fossil-scm.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev
_______________________________________________
fossil-dev mailing list
fossil-dev@lists.fossil-scm.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to