strmod-devel Mailing List for The StreamModule System (Page 2)
Status: Alpha
Brought to you by:
omnifarious
Menu
▾
▴
strmod-devel — Any topics relating to the StreamModule system are welcome here
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(6) |
Nov
(5) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(4) |
Feb
(5) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Eric M. H. <ho...@om...> - 2001-03-26 18:03:47
|
I'm back from the IETF conference. I had fun and learned a lot there. The IETF is an interesting and unique organization. :-) Anyway, I'll be manning #StrMod on irc.openprojects.net again. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-03-18 14:46:04
|
I'll be away at the IETF (http://www.ietf.org) this week, and so I won't be showing up as much on IRC and will probably not be releasing some fixes and StreamModule improvements I've been working on. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-03-06 14:40:14
|
Version 0.2.2 has been released. This version fixes a bug in StreamFDModule. It also adds RouterModule, which is an abstract base class for modules that accept data on several plugs and need to redirect that data to a set of plugs dependendent on the source of the data and the data itself. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-03-05 19:37:37
|
Gavin found a bug in the StreamModule system that had to do with SocketModule or StreamFDModule objects being constructed and destructed in PortForward. I believe I found the bug. I forgot to initialize a bunch of member variables of BufferList in StreamFDModule.cxx The appropriate updates should be in tomorrow's nightly CVS checkout. In the meantime, here's a patch to StreamFDModule that helps. Gavin, thanks a lot for finding the bug for me. :-) Have fun (if at all possible), -- The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hopper) -- |
|
From: Eric M. H. <ho...@om...> - 2001-02-27 11:59:04
|
I had a few bugs in TelnetChunker that I just fixed, and have now released Version 0.2.1. These are the two bugs: 1. It wouldn't pass through 'special' 0 length chunks, which made certain connection strategies based on passing around EOFStrChunk objects not work. 2. It also wouldn't abort a suboption no matter how long it got. While this wouldn't result in a buffer overflow of any kind because of how StrChunks work, it would've resulted in a crash when all available memory was exhausted. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-02-25 14:39:54
|
This release adds a host of improvements began in the 0.1.5 release. The ugly GV_Iterator interface is completely gone and has been replaced by a more flexible Visitor based system. I've also re-written the TelnetParser StreamProcessor. It's been split into TelnetParser, TelnetChunkBuilder and TelnetChunker. TelnetChunker is the processor that does what TelnetParser used to do. This release is not well tested, and there are a lot of major changes, so use it at your own risk. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-02-16 14:50:00
|
This is a rather quiet list because there are only two developers, and we're working on completely different sections, and I've been a little busy with a job transfer recently. That doesn't mean it's not actively read. :-) Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-02-15 17:34:18
|
----- Forwarded message from Pierre Phaneuf <pp...@lu...> ----- Delivered-To: ho...@om... Date: Thu, 15 Feb 2001 11:52:14 -0500 From: Pierre Phaneuf <pp...@lu...> Organization: Ludus Design X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en To: ho...@om... Subject: Why I think CORBA and other forms of RPC are often a bad idea=20 Did you read this? http://advogato.org/article/222.html Or this: http://www3.sympatico.ca/pphaneuf/thread.html I like your article so much that I've certified you journeyer. :-) --=20 "We make rope." -- Rob Gingell on Sun Microsystem's new virtual memory. ----- End forwarded message ----- --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-02-15 17:34:07
|
On Thu, Feb 15, 2001 at 11:52:14AM -0500, Pierre Phaneuf wrote: >=20 > Did you read this? >=20 > http://advogato.org/article/222.html >=20 > Or this: >=20 > http://www3.sympatico.ca/pphaneuf/thread.html >=20 > I like your article so much that I've certified you journeyer. :-) *grin* I very much agree with you about threads. The way threads are usually used is evil. They're used to try to hide asynchronous behavior behind some sort of veneer of synchronousness. This largely fails, and adds a lot of excess overhead. You end up synchronizing with thread primitives instead, and that's just a huge pain, and very error prone. The one useful location for threads are places where you do a lot of computation, and you want that computation to not interfere with the rest of the system's processing. Any desire to help with StreamModule, which can be thought of as both a rudimentary componenet system vaguely based on the 'pipe' idea, and as an exercise in cooperative multithreading? :-) *grin*, --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: ^chewie <ch...@wo...> - 2001-01-23 16:14:01
|
Found a cool OO language today. You've probably heard of it: Ruby.
Sounds like a strong competitor to Python, with quite a few distinct
advantages over Python:
http://www.ruby-lang.org/en/compar.html
Anyway, back to work.
--=20
Chad Walstrom <ch...@wo...> | a.k.a. ^chewie
http://www.wookimus.net/ | s.k.a. gunnarr
Key fingerprint =3D B4AB D627 9CBD 687E 7A31 1950 0CC7 0B18 206C 5AFD
|
|
From: Eric M. H. <ho...@om...> - 2001-01-23 01:36:46
|
I believe I've solved that problem. Now it should only allow mail from list subscribers. I expected that option to be on by default. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2001-01-23 01:08:28
|
Spam, what a revolting development. I'm going to have to figure out how to make this a moderated list. *sigh*, --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: <em...@li...> - 2001-01-23 01:04:23
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=3D(0073)file://C:\WINDOWS\Temporary%20Internet%20File=
s\OLKC225\A0007-1-A2-00.html -->
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-1=
252">
<META content=3D"Microsoft FrontPage 4.0" name=3DGENERATOR>
<META content=3DFrontPage.Editor.Document name=3DProgId></HEAD>
<BODY bgColor=3D#cccccc>
<DIV align=3Dcenter>
<TABLE borderColor=3D#003366 cellSpacing=3D5 borderColorDark=3D#003366 ce=
llPadding=3D14=20
width=3D550 borderColorLight=3D#003366 border=3D2>
<TBODY>
<TR>
<TD width=3D"100%" bgColor=3D#ffffff>
<P class=3DMsoBodyText align=3Dcenter><B><FONT face=3DVerdana color=
=3D#003399=20
size=3D4>Help Beta Test Our Site and Be Eligible to Purchase Shares=
of=20
Future IPOs In Which We Participate**</FONT></B></P>
<P class=3DMsoBodyText style=3D"TEXT-ALIGN: left" align=3Dleft><FON=
T face=3DArial=20
size=3D2>eMedsecurities has selected you as a possible participant =
to help=20
test our online stock-trading engine for knowledge-based investing =
in the=20
life sciences. For your cooperation, <B>you will be eligible =
to purchase=20
shares of future IPOs</B> in which we participate, for as long as y=
ou=20
maintain your account with us. This is limited to only <B>50 =
qualified=20
testers! </B><a href=3D"mailto:eme...@li...">Request M=
ore
Information</a>.**</FONT></P>
<P class=3DMsoBodyText align=3Dcenter><B><FONT face=3DVerdana color=
=3D#003399=20
size=3D3>eMedsecurities=85 The Cure for the Common Portfolio!</FONT=
></B></P>
<P class=3DMsoBodyText style=3D"TEXT-ALIGN: left" align=3Dleft><FON=
T face=3DArial=20
size=3D2>eMedsecurities provides you with a wealth of information, =
all=20
compiled in a single, easy-to-use resource. Learn about new r=
esearch=20
and upcoming treatments for diabetes, glaucoma, cataract, obesity a=
nd much more. Obtain critical investment information about the=20
companies that are developing these treatments. eMedsecuritie=
s empowers=20
you to make more informed investment decisions. <a href=3D"ma=
ilto:eme...@li...">Request
More Information</a>.**</FONT></P>
<P class=3DMsoNormal><B><FONT face=3DArial size=3D2>Participation i=
n
eMedsecurities's Beta Test allows you:</FONT></B></P>
<UL>
<LI>
<P class=3DMsoNormal=20
style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
face=3DArial size=3D2 color=3D"#003399">Eligibility to purchase s=
hares of IPOs in which=20
eMedsecurities participates for as long as you maintain your=20
account**</FONT></B> </P>
<LI>
<P class=3DMsoNormal=20
style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
face=3DArial size=3D2 color=3D"#003399">Valuable research of the =
entire product=20
pipeline of companies, including stages of clinical development, =
by=20
industry or specific disease</FONT></B> </P>
<LI>
<P class=3DMsoNormal=20
style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
face=3DArial size=3D2 color=3D"#003399">Useful information about =
industry trends, recent=20
developments and upcoming IPOs</FONT></B> </P>
<LI>
<P class=3DMsoNormal=20
style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
face=3DArial size=3D2 color=3D"#003399">Commitment to customer se=
rvice featuring=20
our Live Customer Service Online</FONT></B> </P>
<LI>
<P class=3DMsoNormal=20
style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
face=3DArial size=3D2 color=3D"#003399">Dedication to fast trade =
executions at the best=20
possible price.</FONT></B> </P>
</UL>
<P align=3Dleft><FONT face=3DArial size=3D2>The following guideline=
s will=20
explain what we expect from an eMedsecurities Beta Tester:</FONT></=
P>
<UL>
<LI>
<P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Open a funded eMedsecurities=20
account</FONT> </P>
<LI>
<P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Visit our online trading site onc=
e=20
a week</FONT> </P>
<LI>
<P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Execute trades through our
Web=20
site in accordance with your normal practice</FONT> </P>
<LI>
<P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Submit feedback to eMedsecurities=
's development team through a questionnaire sent via=20
email</FONT> </P>
<LI>
<P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Provide us with additional=20
feedback regarding the site as needed.</FONT> </P></LI></UL>
<P align=3Dleft><FONT face=3DArial size=3D2>The test is limited to =
only 50 Beta=20
Testers so sign up now to be considered! <a href=3D"mailto:em=
ed...@li...">Request
More Information</a>.**</FONT>=20
<P align=3Dleft><B><FONT face=3DArial size=3D2>Please note:</FONT><=
/B><FONT=20
face=3DArial size=3D2> All applications for the Beta Test must be s=
ubmitted by
January 25, 2001 to be considered.</FONT>=20
<P align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
style=3D"mso-bidi-font-size: 12.0pt; mso-fareast-font-family: Times=
New Roman; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bi=
di-language: AR-SA">Please=20
be advised that your information will stay in our proprietary datab=
ase and=20
will not be sold, traded, given or otherwise provided to outside ve=
ndors.
We respect your privacy.</SPAN></FONT>=20
<P align=3Dleft>=20
<P align=3Dleft><FONT face=3DArial size=3D1><SPAN=20
style=3D"mso-fareast-font-family: Times New Roman; mso-ansi-languag=
e: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">By=20
submitting your information, you implicitly state that this is some=
thing=20
that interests you and that you<br>
agree to receive periodic emails from=20
eMedsecurities.</SPAN></FONT>=20
<P class=3DMsoNormal><FONT face=3DArial size=3D1>Research indicated=
that you=20
might benefit from our offer. To be removed instantly and per=
manently from=20
our database, simply <a href=3D"mailto:em...@li...">click here=
</a>.
We respect=20
all removal requests.</FONT></P><FONT face=3DArial size=3D1>**<B> R=
estrictions=20
Apply:</B> <SPAN style=3D"COLOR: red"><B>Beta test not open t=
o residents
of HI, IL, MI, MN, NE, NH, TN, TX.</B></SPAN> Initial Public=20
Offerings are considered speculative investments and as such may no=
t be=20
appropriate for every investor. If an investor chooses to participa=
te in=20
IPOs, there are certain restrictions that apply. <B><SP=
AN=20
style=3D"COLOR: red">Flipping </SPAN>- </B>The first time an invest=
or sells
their shares within the first 30 days the issue is trading in the=20
secondary market, that investor will not be allocated shares for th=
e next=20
90 days following the sale. The second time that investor =93=
flips,"=20
they will not be allocated IPO shares for 180 days. The third=
time=20
that investor =93flips," they lose their IPO allocations perma=
nently.<SPAN=20
style=3D"COLOR: red"> <B>Transferring shares</B></SPAN><B><sp=
an style=3D"color: red">
</span>- </B>If the=20
investor transfers IPO shares out of their account within the first=
30=20
days the issue is trading in the secondary market, they will perman=
ently=20
lose their IPO allocations. <B>Beta investors will be chosen =
from=20
all the applicants based on their income, net worth and investing=20
experience. </B> Beta Test open only to those 21 years of age=
or
older. IPO shares will only be allocated from transactions in=20
which eMedsecurities participates in the underwriting. A0009-=
1-A2</FONT>
<p><FONT face=3DArial size=3D1>
eMedsecurities, Inc. Member NASD SIPC. </FO=
NT></p>
</TD></TR></TBODY></TABLE></DIV></BODY></HTML>
|
|
From: Chad '^c. W. <ch...@wo...> - 2000-12-11 13:57:42
|
On Sun, Dec 10, 2000 at 10:54:16PM -0600, Eric M. Hopper wrote:
> I've almost finished ripping out all the old GroupVector and
> GV_Iterator stuff on the trunk. I haven't tested any of it yet
> though. It compiles! *grin*
Woohoo! ;-) Compiling is a good thing. ;-)
> I think I'm going to complete redo TelnetParser to have a much
> simpler parsing algorithm that tries less hard to be optimal.
> Premature optimization is the root of all programming evil. :-)
Heh. I'll remember that. Good news. I think I can put some time in
tonight on the library. ;-) If I don't get stuck at work too late
tonight, unlike all last week, I'll throw in a few hours before
meeting a school friend of mine at the bars tonight. ;-)
How's things goin' otherwise?
--=20
Chad "^chewie, gunnarr" Walstrom <ch...@wo...>
http://www.wookimus.net/
|
|
From: Eric M. H. <ho...@om...> - 2000-12-11 04:54:18
|
I've almost finished ripping out all the old GroupVector and GV_Iterator stuff on the trunk. I haven't tested any of it yet though. It compiles! *grin* I think I'm going to complete redo TelnetParser to have a much simpler parsing algorithm that tries less hard to be optimal. Premature optimization is the root of all programming evil. :-) Have fun all, --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2000-11-19 13:40:47
|
On Sat, Nov 18, 2000 at 11:45:24PM -0600, Chewie wrote: > On Sat, Nov 18, 2000 at 09:16:14PM -0600, Eric M. Hopper wrote: > > In the meantime... > >=20 > > I executed these commands: > >=20 > > cvs rtag -r LIBNET_V_0_1_5 chad_streamfd_poll-pre-branch libNet > > cvs rtag -r LIBNET_V_0_1_5 -b chad_streamfd_poll-branch libNet >=20 > *chewie@skuld:~/checkout/libNet$ cvs update -r chad_streamfd_poll-branch = -d -P > ch...@om...'s password:=20 > cvs [server aborted]: cannot write > /home/hopper/src/cvs/CVSROOT/val-tags: Permission denied >=20 > Looks like a little permissions problem. Fixed. I have no idea what val-tags is for though. How odd. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Chewie <ch...@wo...> - 2000-11-19 05:46:22
|
On Sat, Nov 18, 2000 at 09:16:14PM -0600, Eric M. Hopper wrote:
> In the meantime...
>=20
> I executed these commands:
>=20
> cvs rtag -r LIBNET_V_0_1_5 chad_streamfd_poll-pre-branch libNet
> cvs rtag -r LIBNET_V_0_1_5 -b chad_streamfd_poll-branch libNet
*chewie@skuld:~/checkout/libNet$ cvs update -r chad_streamfd_poll-branch -d=
-P
ch...@om...'s password:=20
cvs [server aborted]: cannot write
/home/hopper/src/cvs/CVSROOT/val-tags: Permission denied
Looks like a little permissions problem.
--=20
Chad "^chewie, gunnarr" Walstrom <ch...@wo...>
http://www.wookimus.net/
|
|
From: Eric M. H. <ho...@om...> - 2000-11-19 03:16:17
|
On Sat, Nov 18, 2000 at 01:44:00PM -0600, Chewie wrote: > I see libNet's most recent version is LIBNET_V_2_0. There's a few > other tags available, but this seems to be the one pertaining to the > "stable" version. Before I continue, I propose the following: The current version of libNet is 0.1.1. The NETLIB tags are from an older naming scheme that I've abandon. > * Use Linux kernel-style versioning management: major.minor.patch Done. :-) > * Tag the main/HEAD branch with a relative tag called "stable" I don't think my system has enough users to be considered stable. :-) > * Tags that do not reference the full version are relative tags > and move to the head of the release versions. >=20 > - LIBNET_V_2_0_x references patch release of stable branch > - LIBNET_V_2_0 references head of v2.0 stable branch > - LIBNET_V_2 references head of v2 branch > - LIBNET references head of stable branch > - stable references head of stable branch >=20 > - LIBNET_V_2_1_x references patch release of unstable branch > - LIBNET_V_2_1 references head of v2.1 unstable branch > - unstable references head of unstable branch I would prefer all branch tags end in '-branch'. A x.even.*/x.odd.* for determining stable vs. unstable releases is a good idea. > * Branch at first release of stable for unstable >=20 > - LIBNET_V_2_1_0 branched at LIBNET_V_2_0_0 I think there ought to be a branch tag called LIBNET_V_0_2-branch. I think the 'stable' series should be considered the branch, and the 'unstable' series be considered the mainline. I think named branches for particular long-running alterations, such as my addition of the Visitor code, are a good idea. Such branches should not be named with a version numbering scheme. > * Main version branches should only contain compilable and useable > code. Therefore, in-development patches should branch from the > previous patch release tags until their code can be merged into > the main branches. The name of these branches should reflect > which patch level they originated from and purpose for the > branch. >=20 > - LIBNET_V_2_0_11-bugfix_1101 branched from LIBNET_V_2_0_11 for > development of the #1101 bugfix. > - LIBNET_V_2_1_0-streamfd_poll for Chad's work on > StreamFDModule, started at v2.1.0 This is also a workable scheme for maintaining long-running changes in a seperate branch as well. All such long-running changes should be a branch of the main branch. The only thing that should go into the stable branches are known working patches. I would be hesitant to allow a branch of the stable release branch. > * When the patch-level branches are ready to merge, time may have > passed by and a number of patch releases may have been > incorporated already. For example, bugfixes #1453 (started at > v2.0.1) and #1555 (started at v2.0.2) were merged with the > stable branch and the new release tag was issued for v2.0.5. >=20 > So, how do we merge in these two bug fixes w/o polluting the > main trunk? We make a staging point branch. This branch we can > assume is no where near stable or compilable. The staging point > branches from the last release. The developers are then > responsible for merging in their changes to this branch. > (Personally, I hate the 'pre' tag because it gets misinterpreted > and misused, although it may be appropriate in this case.) >=20 > - LIBNET_V_2_0_5-merging >=20 > Once the merging branch is complete and compilable, then it is > merged in with the main branch and a new release tag is created. >=20 > - LIBNET_V_2_0_5 >=20 > Now, I don't know if this too many things to keep track of as far as > branches are concerned, but I think it does a few things for us: >=20 > * Isolates unstable code from stable code >=20 > * Isolates patch code from release code >=20 > * Guarantees that the unstable and stable branches ALWAYS have > compilable code. Even at the HEAD of the branch. >=20 > * Allows us to track the origin of the patch-level code, while not > placing any pre-conceived notions as to when it'll get merged > into the main branch. =20 >=20 > * Allows multiple bug-fixes and branches to be in development at > the same time. >=20 > Let me know what you think... Having a particular system for handling branches is a good idea. I think yours is a little more complex than is needed. I will think on this and come up with a scheme. It will incorporate a Linux kernel style odd/even unstable/stable numbering scheme. It will also incorporate a braching scheme so that it's always possible to check out the latest revision in a stable line. In the meantime... I executed these commands: cvs rtag -r LIBNET_V_0_1_5 chad_streamfd_poll-pre-branch libNet cvs rtag -r LIBNET_V_0_1_5 -b chad_streamfd_poll-branch libNet in order to create a branch for you to use for your modifications to make streamfd module use events instead of polling. This creates a branch from the last semi-stable version (0.1.5) that you can use to do your work in. The naming scheme for long-term modifications requiring a branch should probably be firmed up, but, with the number of developers we have, I think the 'making it up as we go along' method will suffice. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Chewie <ch...@wo...> - 2000-11-18 19:44:55
|
I see libNet's most recent version is LIBNET_V_2_0. There's a few
other tags available, but this seems to be the one pertaining to the
"stable" version. Before I continue, I propose the following:
* Use Linux kernel-style versioning management: major.minor.patch
* Tag the main/HEAD branch with a relative tag called "stable"
* Tags that do not reference the full version are relative tags
and move to the head of the release versions.
- LIBNET_V_2_0_x references patch release of stable branch
- LIBNET_V_2_0 references head of v2.0 stable branch
- LIBNET_V_2 references head of v2 branch
- LIBNET references head of stable branch
- stable references head of stable branch
- LIBNET_V_2_1_x references patch release of unstable branch
- LIBNET_V_2_1 references head of v2.1 unstable branch
- unstable references head of unstable branch
* Branch at first release of stable for unstable
- LIBNET_V_2_1_0 branched at LIBNET_V_2_0_0
* Main version branches should only contain compilable and useable
code. Therefore, in-development patches should branch from the
previous patch release tags until their code can be merged into
the main branches. The name of these branches should reflect
which patch level they originated from and purpose for the
branch.
- LIBNET_V_2_0_11-bugfix_1101 branched from LIBNET_V_2_0_11 for
development of the #1101 bugfix.
- LIBNET_V_2_1_0-streamfd_poll for Chad's work on
StreamFDModule, started at v2.1.0
* When the patch-level branches are ready to merge, time may have
passed by and a number of patch releases may have been
incorporated already. For example, bugfixes #1453 (started at
v2.0.1) and #1555 (started at v2.0.2) were merged with the
stable branch and the new release tag was issued for v2.0.5.
So, how do we merge in these two bug fixes w/o polluting the
main trunk? We make a staging point branch. This branch we can
assume is no where near stable or compilable. The staging point
branches from the last release. The developers are then
responsible for merging in their changes to this branch.
(Personally, I hate the 'pre' tag because it gets misinterpreted
and misused, although it may be appropriate in this case.)
- LIBNET_V_2_0_5-merging
Once the merging branch is complete and compilable, then it is
merged in with the main branch and a new release tag is created.
- LIBNET_V_2_0_5
Now, I don't know if this too many things to keep track of as far as
branches are concerned, but I think it does a few things for us:
* Isolates unstable code from stable code
* Isolates patch code from release code
* Guarantees that the unstable and stable branches ALWAYS have
compilable code. Even at the HEAD of the branch.
* Allows us to track the origin of the patch-level code, while not
placing any pre-conceived notions as to when it'll get merged
into the main branch. =20
* Allows multiple bug-fixes and branches to be in development at
the same time.
Let me know what you think...
--=20
Chad "^chewie, gunnarr" Walstrom <ch...@wo...>
http://www.wookimus.net/
|
|
From: Chewie <ch...@wo...> - 2000-11-04 11:52:19
|
I'm finally getting around to throwing in the towel on recovering
my harddrive data. Lesson learned hard. NEVER kill your parition
table if you don't have a backup or at least a map of the sectors!
*sigh*
Anyway, I'm also getting around to finally reinstalling my system
from scratch and rolling in the backup from August. (I've REALLY
got to be more loyal to my backups.
--
Chad "^chewie, gunnarr" Walstrom <ch...@wo...>
http://www.wookimus.net/
|
|
From: Eric M. H. <ho...@om...> - 2000-10-28 02:29:52
|
http://www.omnifarious.org/StrMod/doxygen Yes, it's different from the last time I told you to go look. Play around for a bit. Wow! Doxygen does an incredible job of generating class documentation. I'm at something of a loss for words. When combined with what GraphViz (http://www.research.att.com/sw/tools/graphviz/) can do, it's nothing short of amazing. It generates useful diagrams even if you don't actually have any documentation. Anyway, I urge all of you to go have a look. :-) It looks best in a browser that has decent support for style sheets. Mozilla, or (I think) IE 4.5 or later. Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: Eric M. H. <ho...@om...> - 2000-10-17 17:54:57
|
I've started converting the documentation comments in the
StreamModule system over to Doxygen format. Doxygen is MUCH nicer than
the old system I used, Perceps.
But, because doxygen uses css, it's best viewed with Mozilla or
Galleon, or *shudder* recent versions of IE.
http://www.omnifarious.org/StrMod/doxygen/
Have fun (if at all possible),
--=20
The best we can hope for concerning the people at large is that they
be properly armed. -- Alexander Hamilton
-- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe=
r) --
|
|
From: ^chewie <ch...@wo...> - 2000-10-17 17:42:43
|
Just making sure I'm still subscribed to the list.
--=20
Chad "^chewie, gunnarr" Walstrom <ch...@wo...>
http://wookimus.net/chewie
|
|
From: Eric M. H. <ho...@om...> - 2000-10-17 12:43:19
|
But, because doxygen uses css, it's best viewed with Mozilla or Galleon. http://www.omnifarious.org/StrMod/doxygen/ Have fun (if at all possible), --=20 The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper (ho...@om... http://www.omnifarious.org/~hoppe= r) -- |
|
From: ^chewie <ch...@wo...> - 2000-10-06 23:42:13
|
Hey, Eric. I tried to log on to omnifarious.org and couldn't get past the login. The password that I have recorded is apparently not the same as the one on the server. Either that, or you've rotated passwords or have some other restriction on teh sshd server. Could you fix this please? Email me another password via pgp. Thanks. --=20 Chad "^chewie, gunnarr" Walstrom <ch...@wo...> http://wookimus.net/chewie |
