On Sat, 3 Mar 2018 10:58:28 -0600 "Edward K. Ream" <[email protected]> wrote:
> On Sat, Mar 3, 2018 at 10:52 AM, Terry Brown <[email protected]> > wrote: > > Not that it's a reason not to document as I go, but the project's far > > from finished. It aspires to replace: > > [snip] > > Is there any reason not to create an issue for this? No, I should probably do that to clarify current subtasks. > I'm confused. Why delete the branch if the project isn't finished? > > Edward I guess recent work had been done in devel (master) and I figured I'd keep doing it there. Feature branches are good for isolating things that are non-functional or broken or likely to cause disruption, but things like this that are fairly inert unless you specifically activate them, working in devel doesn't seem to pose any major risk of harm. The upside for keeping the branch would be grouping all the commits related to this work "together", although you can also get that by looking for commits touching certain files. Maybe it would be worth doing that, although I think that horse has bolted as far as this particular project is concerned. The downside is the admittedly minor chore of merging to devel when putting new features out for testing etc. The branch can be recreated of course, although if recent commits are in devel there will be a hole in it lineage wise. Cheers -Terry -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
