Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 107 of 807  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject Text Attachments
  605   Wed Jul 14 22:59:05 2004 Idea Steve Jonessteve.jones@freescale.comQuestionAll2.5.3Re: Question on how "Format <attribute> = " works> Just have a look at elog:571 which should
answer your question. Also look at
> elog:Config+Examples/4 which is the configuration
  
  610   Fri Jul 16 04:36:51 2004 Agree Steve Jonessteve.jones@freescale.comQuestionAll2.5.3Re: Question on how "Format <attribute> = " works> > Ok, I think I see now.  I was assuming
it applied to the entry form as well.
  
  611   Fri Jul 16 04:37:47 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.3Re: Possible Formatting bug: Summary view> > A temporary fix for this is to set summary
lines = 0
  
  613   Fri Jul 16 16:53:01 2004 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.5.3Date format problem in "Thread display = "I have an attributes defined as:

 - Attributes = Author, PlannedDate, FunctionalArea,
  
  614   Fri Jul 16 17:51:52 2004 Idea Steve Jonessteve.jones@freescale.comRequestAll2.5.3WISHLIST: Type <attribute> = userSomething to add to the wishlist:

- Type <attribute> = user
  
  615   Fri Jul 16 19:06:35 2004 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.5.3BUG?: Preset text = causes replication of text when re-editing a logbook entry.With the "Preset text = " specified, when
re-editing a logbook entry (say to
correct a spelling error) the text of the
  
  624   Wed Jul 28 18:25:32 2004 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.5.4?getcfg problem in v1.410: Truncation of long config stringsJust compiled 1.410 and have run into an issue
that *may* have been
introduced in 1.393.
  
  631   Wed Jul 28 22:07:31 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.4?Re: getcfg problem in v1.410: Truncation of long config strings> > Just compiled 1.410 and have run into
an issue that *may* have been
> > introduced in 1.393.
  
ELOG V3.1.5-3fb85fa6