On Thu, Feb 21, 2008 at 2:51 PM, Derek Atkins <[EMAIL PROTECTED]> wrote:
> svn propedit svn:log -r 16947 --revprop
>
That didn't seem to work...
$ svn propedit svn:log -r 16947 --revprop
svn: DAV request failed; it's possible that the repository's
pre-revprop-change hook either failed or is no
On Thu, Feb 21, 2008 at 3:30 PM, Derek Atkins <[EMAIL PROTECTED]> wrote:
> Ah right. Sorry. I've updated the log message for you.
> Note that it wont show up in trac for a while.
>
Thanks. The good news is that I've figured out the nasty command that I have
to use to get my editor to work prope
Ah right. Sorry. I've updated the log message for you.
Note that it wont show up in trac for a while.
-derek
Quoting Charles Day <[EMAIL PROTECTED]>:
> On Thu, Feb 21, 2008 at 2:51 PM, Derek Atkins <[EMAIL PROTECTED]> wrote:
>
>> svn propedit svn:log -r 16947 --revprop
>>
>
> That didn't seem
Hi,
John M Collins <[EMAIL PROTECTED]> writes:
> Please CC a reply to my email address jmc AT xisl DOT com as I am not
> subscribed
>
> I am trying to build GNUCash 2.2.3 on my Opteron machine which is
> running Mandriva 2007.0
>
> I hit some problems with it crashing on startup and searching you
svn propedit svn:log -r 16947 --revprop
-derek
"Charles Day" <[EMAIL PROTECTED]> writes:
> The message logged during my first SVN commit has been garbled due to my
> editor (vim) and the "svn commit" command not playing well together. Could
> an SVN administrator please correct the log entry fo
"Charles Day" <[EMAIL PROTECTED]> writes:
> On Sun, Jan 20, 2008 at 9:30 PM, Charles Day <[EMAIL PROTECTED]> wrote:
>
>> Here's a patch of miscellaneous updates to whitespace, comments, and
>> "display" text for qif-parse.scm (part of the QIF importer). I have
>> also corrected the default return
Mike--
Good explanation of changing report options. I believe that there's room for
interface/help improvement with report options; there have been several threads
from people with just this problem. I think it derives from the fact that many
people have become accustomed to setting report options
Al Hawley wrote:
>
> ...
> I looked at edit->preferences->"Accounting Period" to find where date
> ranges can be set. Changing the ranges here had no visible effect on the
> date ranges in several reports that I used for testing.
> ...
>
Note that some reports (most notably the Account Repo
Mark Johnson wrote:
> PostgreSQL gives a warning for '', but accepts it; it prefers \'. MySql
> takes the ''; I'm not sure about \'. Obviously SQLite won't take the \'.
>
> However, the real problem is that it is not gnucash-gda code which is
> doing the escaping of the single quote. It is lib
On Sun, Jan 20, 2008 at 9:30 PM, Charles Day <[EMAIL PROTECTED]> wrote:
> Here's a patch of miscellaneous updates to whitespace, comments, and
> "display" text for qif-parse.scm (part of the QIF importer). I have
> also corrected the default return value in the date parsing procedure,
> qif-parse:
Al,
The problem is unclear documentation? I put it that way because
obviously not adequate to get you to the right spot.
That's not "customization" and it is via "options" that you get to
set things each time you run a report -- things like the date range,
what subtotals you want to see
Michael Vrable wrote:
> On Wed, Feb 20, 2008 at 09:34:34PM -0700, Mark Johnson wrote:
>
>> PostgreSQL gives a warning for '', but accepts it; it prefers \'.
>> MySql takes the ''; I'm not sure about \'. Obviously SQLite won't
>> take the \'.
>>
>
> What version of PostgreSQL is this? I
Graham Menhennitt wrote:
> Mark Johnson wrote:
>
>> PostgreSQL gives a warning for '', but accepts it; it prefers \'. MySql
>> takes the ''; I'm not sure about \'. Obviously SQLite won't take the \'.
>>
>> However, the real problem is that it is not gnucash-gda code which is
>> doing the esc
13 matches
Mail list logo