So if someone gets a non-sentinel file from git and changes it -- how do those changes get processed against the sentinel-ed file and get posted as a new sentinel file along with a new sha-1?
On Tue, Feb 11, 2014 at 11:56 AM, Seth Johnson <[email protected]> wrote: > Holy F*! > > On Tue, Feb 11, 2014 at 11:44 AM, Edward K. Ream <[email protected]> wrote: >> On Tue, Feb 11, 2014 at 10:16 AM, Edward K. Ream <[email protected]> >> wrote: >>> >>> >>> The obvious place for the #leo-data line is either the first or last line >>> of the file, but it could occur anywhere. >> >> >> Hahaha. The line need not appear in the file at all! The sha1 key is >> computed from the file's contents, so all we need is a dict associating >> files with their latest sha1 keys. No change *whatever* needed to existing >> files! >> >> We can build the machinery needed to access the central DB into Leo itself. >> Most likely, it will just use git to do the dirty work. >> >> It's kinda shocking how easy it has turned out to be... >> >> Edward >> >> -- >> You received this message because you are subscribed to the Google Groups >> "leo-editor" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/leo-editor. >> For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
