[patch 0/4] Initial batch of minor patches
warlord at MIT.EDU
Sun Jul 24 13:12:34 EDT 2005
Yea, I noticed that.. these are against g2, right?
IMHO I don't think you need to keep re-sending patches unless someone gets back
to you that it needs to be changed. :) What you did here was just fine.
Sending a link is actually more difficult for us.
Also, any chance you could send in an actual ChangeLog message in your patches?
Quoting Chris Shoemaker <c.shoemaker at cox.net>:
> Weird. The patches I sent out a day earlier arrived 3 days later.
> I guess my ISP's mail servers were having problems.
> In general, I almost always keep the current version of all my patches
> updated so that they apply to CVS, but once I email them they may no
> longer apply as cleanly as they did when I mailed them (although they
> usually would). Should I try to email links to my updated version or
> just let whoever commits deal with the occassional fuzz, offsets or
> (rare) failed hunks?
> On Thu, Jul 21, 2005 at 11:44:40PM -0400, c.shoemaker at cox.net wrote:
> > I'm trying out for the first time the patch mailing capability in quilt.
> Let me know if the format is inconvenient.
> > I'd like to start pushing out some of the patches that aren't related to
> budgeting or the register re-write, so here is an initial set of four.
> > -chris
> > --
> > _______________________________________________
> > gnucash-patches mailing list
> > gnucash-patches at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-patches
> gnucash-patches mailing list
> gnucash-patches at gnucash.org
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
More information about the gnucash-devel