Hi Robert,

Sorry, I was unclear.  I was referring to how Martin Owens requested
documentation be submitted as patches instead of random emails to the
list.  I didn't mean to submit logs as patches.  Documenting
the protocol is something that is lacking, so any help folks can provide
is welcome.

For an example, see how Martin documented the Content Store records
under doc/barry-research.ods, and how Nicolas documented javaloader
in doc/javaloader.

As for full logs, it is likely best to put them on a website somewhere
and post a notice to the mailing list so everyone knows about them.
Once someone has gone through the raw logs and figured out the gold
nuggets, they can write a more concise document that goes under doc/.

I was tempted to open a secondary git repo for just logs like this, but
I think that could get out of hand, for size.  repo.or.cz only gives
projects about 100megs, which is tons for source code, but could
get used up quick with 20meg compressed logfiles. :-)

So I think it might be better to put a page under the Barry docs on
netdirect.ca, for straight downloads.  Would anyone find that useful?

I grabbed your javaload_multiple_files.txt.bz2 log.  If you can post
the wipe+kernel_load log to mediafire again, I can grab that too.

Thanks!
- Chris


On Fri, Jan 23, 2009 at 06:50:12PM -0600, Robert Yaklin wrote:
> How would I go about submiting a 20MB log file as a patch? Would I do
> that with CVS? Would I need a non-anonymous login to do so?
> I'd like to submit a log file of a wipe and of loading the Kernel/OS
> which are the two steps that would be done before loading the .cod
> files.
> 
> On 1/23/09, Chris Frey <cdf...@foursquare.net> wrote:
> > On Fri, Jan 23, 2009 at 01:52:50PM -0600, Robert Yaklin wrote:
> >> I made a sniff file using javaloader.exe to load all the files that
> >> would be loaded to a BlackBerry 8700g for a base install of 4.2.1.107.
> >> Even compressed it is a large file so I uploaded it to
> >> http://www.mediafire.com/?twtt3xuzyct instead of attaching it to this
> >> email.
> >
> > Thanks very much for posting these.  I'm still unclear as to the content
> > of the earlier logs you mentioned... would it be worth it to post those
> > as well?
> >
> > - Chris
> >
> >
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by:
> > SourcForge Community
> > SourceForge wants to tell your story.
> > http://p.sf.net/sfu/sf-spreadtheword
> > _______________________________________________
> > Barry-devel mailing list
> > Barry-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/barry-devel
> >
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to