On Mon, Jun 22, 2015 at 2:19 PM, jan i <j...@apache.org> wrote: > Hi > > I agree with Gabriela since it sounds bigger, push it to a branch (no > special naming conventions). > > Smaller patches (bug fixes mostly) to the running code, should be committed > directly to master (only peter transfers > from master to stable from time to time). > > Looking forward to see your work. > rgds > jan i. > > Ps. Gabriela are you still helping ian, or looking for other work ? > > > Both. Got caught a bit by my Logmessage Scribe, just needs a few finishing touches (she says) and I have it running on Google Apps. Just adding a little python patch interpreter, then I'm good to go. Also has a small cmake interpreter, but I'm not sure what kind of patch analysis is useful here for a log message.
Will resurface in a few days ;-) G > > On 22 June 2015 at 15:14, Gabriela Gibson <gabriela.gib...@gmail.com> > wrote: > > > I'd say make a branch, and then push in small increments, whenever you > have > > something ready baked. > > > > A huge patch usually is hard to read (at least I find that) > > > > G > > > > On Mon, Jun 22, 2015 at 2:04 PM, Ian C <i...@amham.net> wrote: > > > > > No I'm not quite going to give birth, at least not in the usual sense. > > > > > > Do we have any formality about when to push changes? > > > I have an ODF version that follows the Word lenses pattern and > > > processes a headers and paragraphs document. One way... that is > > > generates a html. > > > > > > Should I push it? To master? Create a branch? > > > > > > Or shall we try to agree on a different functional target? > > > > > > -- > > > Cheers, > > > > > > Ian C > > > > > > > > > > > -- > > Visit my Coding Diary: http://gabriela-gibson.blogspot.com/ > > > -- Visit my Coding Diary: http://gabriela-gibson.blogspot.com/
