On Sun, May 26, 2013 at 4:01 PM, Erik Huelsmann wrote:
>
> On May 26, 2013 11:59 PM, "Brian Wolf" wrote:
> >
> > >>I am trying to figure out the best way to support easy shipping after
> billing. The big problem right now is that unless and until we
> >>completely re-engineer both the invoice a
This is for custom menu generation functions. For example, if you wanted a
special routine to build menus for mobile devices this is where you would
build it (and patch the rest of the app to direct here).
Best Wishes,
Chris Travers
On Sun, May 26, 2013 at 8:49 AM, Brian Wolf wrote:
> I see t
My accounting background is limited;
I'm much more familiar with business operations workflow. So I'm
not sure how to answer the question.
Thanks.
Brian
Brian Wolf
On May 26, 2013 11:59 PM, "Brian Wolf" wrote:
>
> >>I am trying to figure out the best way to support easy shipping after
billing. The big problem right now is that unless and until we
>>completely re-engineer both the invoice and order logic, getting a
perfect solution in place is going to be a
>>I am trying to figure out the
best way to support easy shipping after billing. The big problem
right now is that unless and until we >>completely
re-engineer both the invoice and order logic, getting a perfect
solution in place is going to be a prohibitively la
Hi chris,
Answering the mail below has been on my list of things to do for a long
time. I hope to clean out my backlog today.
> I am trying to figure out the best way to support easy shipping after
billing. The big problem right now is that unless and until we completely
re-engineer both the inv
I see that there is a reference to a custom menu PERL script at the
bottom of menu.pl:
eval { do "scripts/custom/menu.pl"};
Can someone provide me with some background information on
what the script should return (or print or whatever
Just as a note for future reference
If I understand the patch and its relationship with other patches, this is
the sort of thing that really should get into a new RC since it is a fix to
a fix and thus, we hope, reduces regressions.
Best Wishes,
Chris Travers
-
Yes, we can do an RC2 tomorrow, actually. I don't think it will even delay
a release since we probably want to make sure that people have a real
chance to test.
Best Wishes,
Chris Travers
On Sun, May 26, 2013 at 2:34 AM, herman vierendeels <
herman.vierende...@gmail.com> wrote:
> Hi Chris,
>
>
Hi Chris,
could i still commit following:
Index: bin/ir.pl
===
--- bin/ir.pl(revision 5868)
+++ bin/ir.pl(working copy)
@@ -39,7 +39,6 @@
#==
use LedgerSMB
Hi everyone;
1.3.33 rc1 is out. I have made some changes to the changelog since
building the tarball but these are documentation changes No need to reset
the freeze for release clock for that.
This release corrects another 1.3 regression discovered by John Locke which
causes issues with check
11 matches
Mail list logo
