Re: Experiment: use README.MD to document branches

2017-07-08 Thread Edward K. Ream
On Sat, Jul 8, 2017 at 10:10 AM, Terry Brown wrote: > There is a simple workaround. Don't *replace* the standard readme, > > *add *the branch description *in front of* the standard readme file. > > One option: > > https://stackoverflow.com/a/3970442/1072212 > > another approach: > > https://stack

Re: Experiment: use README.MD to document branches

2017-07-08 Thread Terry Brown
On Sat, 8 Jul 2017 06:34:26 -0700 (PDT) "Edward K. Ream" wrote: > > > On Saturday, July 8, 2017 at 12:50:22 AM UTC-5, Edward K. Ream wrote: > > > > On Sunday, July 2, 2017 at 6:32:34 AM UTC-5, Edward K. Ream wrote: > > > > > Changing README.MD seems to be the simplest way to keep track of > > >

Re: Experiment: use README.MD to document branches

2017-07-08 Thread Edward K. Ream
On Saturday, July 8, 2017 at 12:50:22 AM UTC-5, Edward K. Ream wrote: > > On Sunday, July 2, 2017 at 6:32:34 AM UTC-5, Edward K. Ream wrote: > > > Changing README.MD seems to be the simplest way to keep track of the > purpose and status of a branch. > > Alas, merging a branch into master over-w

Re: Experiment: use README.MD to document branches

2017-07-07 Thread Edward K. Ream
On Sunday, July 2, 2017 at 6:32:34 AM UTC-5, Edward K. Ream wrote: > Changing README.MD seems to be the simplest way to keep track of the purpose and status of a branch. Alas, merging a branch into master over-writes the readme file in master. Naturally, this can be undone, but if it *isn't*

Re: Experiment: use README.MD to document branches

2017-07-02 Thread Edward K. Ream
On Sun, Jul 2, 2017 at 8:02 AM, vitalije wrote: > Ok, it is on my to-do list for sqlite-format branch. > ​Thanks. 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

Re: Experiment: use README.MD to document branches

2017-07-02 Thread vitalije
Done at 96456e8 for sqlite-format branch. -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send ema

Re: Experiment: use README.MD to document branches

2017-07-02 Thread vitalije
Ok, it is on my to-do list for sqlite-format branch. Vitalije -- 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 leo-editor+unsubscr...@googlegroups.com. To post to t

Experiment: use README.MD to document branches

2017-07-02 Thread Edward K. Ream
Changing README.MD seems to be the simplest way to keep track of the purpose and status of a branch. I don't know of any other way. I've just changed this file for the new mark-point branch . See the end of the page. If there are confli