upcoming patches

[Derek Atkins]

If you anticipate discussion you should have that discussion here.  If you
really expect a patch to warrant discussion, then you should discuss it here
first before you expend the effort to create the patch.

The -patches list isn't for discussion, really.

-derek

Quoting Chris Shoemaker <c.shoemaker at cox.net>:

> 
> I didn't feel like coding last night so I've tried to clear some of
> the fuzz out of my g2 tree.  I stuck to the stuff that's completely
> independent of anything I'm seriously working on.  I managed to
> isolate a (depressingly small) portion of the diff into several
> patches, which I will shortly send to gnucash-patches.
> 
> I don't expect this stuff to generate much discussion (hopefully later
> stuff will, though).  However, I'm curious where those discussions would
> normally take place if I send patches to gnucash-patches?  or should I
> send patches to both gnucash-patches and gnucash-devel?  ISTM there's
> almost no discussion on the gnucash-patches list.  Maybe no one has
> anything to say?  :)
> 
> -chris
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 


-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available