From billings at negate.org Thu Dec 21 11:47:24 2000 From: billings at negate.org (Jonathan S Billings) Date: Thu, 21 Dec 2000 11:47:24 -0500 (EST) Subject: [Wplug-web] First Post Message-ID: I have a couple suggestions, and I thought I'd test this list out. The colors have GOT to change. Nobody does Black background web pages anymore. it has to be lighter. From zman at angstrom.net Thu Dec 21 12:31:24 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 21 Dec 2000 12:31:24 -0500 Subject: [Wplug-web] First Post In-Reply-To: ; from billings@negate.org on Thu, Dec 21, 2000 at 11:47:24AM -0500 References: Message-ID: <20001221123124.A3854@angstrom.net> On Thu, Dec 21, 2000 at 11:47:24AM -0500, Jonathan S Billings wrote: > I have a couple suggestions, and I thought I'd test this list out. > > The colors have GOT to change. Nobody does Black background web pages > anymore. it has to be lighter. > > _______________________________________________ > Wplug-web mailing list > Wplug-web at wplug.org > http://www.wplug.org/mailman/listinfo/wplug-web > Woo! First post!! I'm open to color change. Although the background isn't really black.. what would we like to use? White? I think we need to php'ize it, so we can have a php header and footer file w/ body tags etc, that are called with a simple include line. -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Thu Dec 21 12:36:23 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 21 Dec 2000 12:36:23 -0500 Subject: [Wplug-web] Anonymous Bk access Message-ID: <20001221123623.B3854@angstrom.net> I'm in the process of getting help from various bk folks in setting up an anonymous access repository that people can grab w/o grabbing files w/ sensitive data (passwords). What files should we exclude? Obviously the conf,admin, and announcements directories. What else? Billings: Do you have bk working yet? Just to clarify /users/zman/public_html/wplug.zman is where we are going to do the design work and eventually merge to /home/www The readonly anonymous repository will be /users/zman/anonymous After every update to wplug.zman someone will have to go into anonymous and do a pull. If you commit something, you're responsible for updating anonymous. We can probably script it somehow. I have this setup on my system now, and will get it on wplug.org later tonight. -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Thu Dec 21 12:40:05 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 21 Dec 2000 12:40:05 -0500 Subject: [Wplug-web] Anonymous bk access Message-ID: <20001221124005.C3854@angstrom.net> This is a possible solution: ----- Forwarded message from Larry McVoy ----- X-From_: lm at bitmover.com Thu Dec 21 12:04:02 2000 Date: Thu, 21 Dec 2000 09:03:57 -0800 From: Larry McVoy To: Zach Paine Cc: bitkeeper-users at bitmover.com Subject: Re: Setting up bk Mail-Followup-To: Zach Paine , bitkeeper-users at bitmover.com X-Mailer: Mutt 1.0pre3i In-Reply-To: <20001221011417.E12497 at angstrom.net> On Thu, Dec 21, 2000 at 01:14:17AM -0500, Zach Paine wrote: > 1. Some of the files in the repository contain sensitive information that > should not be public. > 2. I do not want everyone writing to the repository > > I would rather do the latter, limiting what people can grab to certain files. > Is this possible? BK is currently an "all-or-nothing" model. There isn't any way to filter out some files in a repository. What I would do to deal with this is put the files you are worried about in a different repository (run bk setup again; if they are that sensitive you might want to make it a single user repository so it doesn't log your checkin comments) and then create symlinks in the main repository which point to the other docs. So if you have a tree like my_website/ index.html logo.gif confidential.txt you break it into two trees my_website/ index.html logo.gif confidential.txt -> ../../private_stuff/confidential.txt private_stuff/ confidential.txt THen you can put a BKD running in the my_website one without push or cd permissions. Read that last part again! You want to start the BKD like so cd my_website bk bkd -xcd -xpush -lBitKeeper/log/anonlog that will prevent people from using that bkd to look in ../private_stuff. Read the bkd man page, it talks about all this crud. You might also look at the "parent" man page, it talks about how to use ssh if you want to be super secure. -- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm ----- End forwarded message ----- -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Thu Dec 21 12:45:02 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 21 Dec 2000 12:45:02 -0500 Subject: [Wplug-web] Anonymous Bk access In-Reply-To: <20001221123623.B3854@angstrom.net>; from zman@angstrom.net on Thu, Dec 21, 2000 at 12:36:23PM -0500 References: <20001221123623.B3854@angstrom.net> Message-ID: <20001221124502.E3854@angstrom.net> For now just leave the anonymous stuff up to me (ie. don't worry about updating anonymous) as I'm not sure how we are going to attack these issues yet: 1. Anonymous access can't have passwords in it 2. Anonymous rep has to be the same version as wplug.zman -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D On Thu, Dec 21, 2000 at 12:36:23PM -0500, Zach Paine wrote: > I'm in the process of getting help from various bk folks in setting up an > anonymous access repository that people can grab w/o grabbing files w/ > sensitive data (passwords). What files should we exclude? Obviously the > conf,admin, and announcements directories. What else? > > Billings: Do you have bk working yet? > > Just to clarify > /users/zman/public_html/wplug.zman is where we are going to do the design work > and eventually merge to > /home/www > > The readonly anonymous repository will be /users/zman/anonymous > > After every update to wplug.zman someone will have to go into anonymous and do > a pull. If you commit something, you're responsible for updating anonymous. > We can probably script it somehow. > > I have this setup on my system now, and will get it on wplug.org later > tonight. > -- > Zach Paine > http://www.wplug.org/~zman/zman.key > Key available from pgp.ai.mit.edu ID: 87746D3D > Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D > _______________________________________________ > Wplug-web mailing list > Wplug-web at wplug.org > http://www.wplug.org/mailman/listinfo/wplug-web > From evand at dibiase.org Thu Dec 21 12:51:12 2000 From: evand at dibiase.org (Evan DiBiase) Date: Thu, 21 Dec 2000 12:51:12 -0500 Subject: [Wplug-web] Anonymous Bk access In-Reply-To: <20001221123623.B3854@angstrom.net>; from zman@angstrom.net on Thu, Dec 21, 2000 at 12:36:23PM -0500 References: <20001221123623.B3854@angstrom.net> Message-ID: <20001221125112.A12525@darkcloud.dibiase.org> ::evand is on the computer when he should not be:: On Thu, Dec 21, 2000 at 12:36:23PM -0500, Zach Paine wrote: > After every update to wplug.zman someone will have to go into anonymous and do > a pull. If you commit something, you're responsible for updating anonymous. > We can probably script it somehow. Do it like nightly CVS. Make a script that updates every night (morning) at 12:00, so people can get the latest every night. -- Evan DiBiase PGP/GPG Key Available at http://www.wplug.org/~evand/key.asc Fingerprint: B4BC 503D F988 51E5 C800 2966 21D5 C3DF C4C1 BF64 "Between living and dreaming there is a third thing. Guess it." -Antonio Machado -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://www.wplug.org/pipermail/wplug-web/attachments/20001221/1eb4364f/attachment.bin From zman at angstrom.net Thu Dec 21 12:55:28 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 21 Dec 2000 12:55:28 -0500 Subject: [Wplug-web] Anonymous Bk access In-Reply-To: <20001221125112.A12525@darkcloud.dibiase.org>; from evand@dibiase.org on Thu, Dec 21, 2000 at 12:51:12PM -0500 References: <20001221123623.B3854@angstrom.net> <20001221125112.A12525@darkcloud.dibiase.org> Message-ID: <20001221125528.A4176@angstrom.net> On Thu, Dec 21, 2000 at 12:51:12PM -0500, Evan DiBiase wrote: > ::evand is on the computer when he should not be:: ditto > > Do it like nightly CVS. Make a script that updates every night (morning) > at 12:00, so people can get the latest every night. Then people would have to be accountable for changesets that occured since the last time the script ran.. I didn't phrase that right, but you know what I mean. -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Thu Dec 21 13:02:34 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 21 Dec 2000 13:02:34 -0500 Subject: [Wplug-web] Anonymous BK Access (this is the answer!!) Message-ID: <20001221130234.C4176@angstrom.net> Ok here it is (sumarized): /users/zman/public_html/wplug.zman is the repository we want to use. If you have ssh and an account (us) you can push to it. I can set that up to be a public repository as well running on a specific port so people can: bk clone bk://wplug.org:5000 wplug and get a readonly version. Now in wplug.zman, all of the sensitive files are symlinks to files in another repository, lets say wplug.confidential. When users grab the anonymous stuff, because they are not allowed to change directories, they won't get the sensitive stuff. They can make changes and submit bk patches. As far as us, we can push to both of those repositories! THIS IS IT! /me is excited :) Here is the actual email from the Pres/CEO of BitMover: Later, Zach ----- Forwarded message from Larry McVoy ----- X-From_: lm at bitmover.com Thu Dec 21 12:57:07 2000 Date: Thu, 21 Dec 2000 09:57:05 -0800 From: Larry McVoy To: Zach Paine Cc: bitkeeper-users at bitmover.com Subject: Re: Setting up bk Mail-Followup-To: Zach Paine , bitkeeper-users at work.bitmover.com X-Mailer: Mutt 1.0pre3i In-Reply-To: <20001221124257.D3854 at angstrom.net> > So if someone clones my_website it will be unable to grab the symlinks? This > would prevent people from looking at confidential stuff, but how would the > developers submit patches normally to the website? my_website is set to > -xpush and -xcd so they couldn't do it there could they? The symlinks would propogate, since symlinks are revision controlled by BK, but what they point to would not propogate, that's part of some other repository. As to how your developers would submit patches, that's a very common problem, which I'll restate to make sure I have it right: You want to have a package which you allow the world to read your stuff but restricts write access to a selected few. That's it right? BK gives you a couple of ways to do this; the way everyone does it is this: you use the BKD to give out the read only access and you tell people what the BK url is, i.e., bk://someplace.com:5000 is the foofra project. For the read/write access, those are typically trusted people and you give them ssh access to a machine with a clone into which you allow pushes. Suppose bk://someplace.com:5000 is really someplace.com:/home/bk/foofra, then you give your buddies a login on someplace.com and tell them that the URL they want is someplace.com:/home/bk/foofra, i.e., a bk clone someplace.com:/home/bk/foofra foofra will do what they want and then they can push and it will prompt for a password and allow them to push. BK does have a more obscure way of allowing ssh access. You can set things up so the bkd is actually the login shell. This means that the only thing the user can do is run bkd commands, which is a lot safer than giving them an account on the box. This is how you'd typically integrate BK into something like sourceforge, in fact, that's exactly why we added it. -- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm ----- End forwarded message ----- -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Thu Dec 21 14:39:43 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 21 Dec 2000 14:39:43 -0500 Subject: [Wplug-web] New bk setup Message-ID: <20001221143943.A5684@angstrom.net> Ok. this is how bk has to be setup now. I can't be online all day, and I won't get on until after 11pm tonight. If this isn't done by then, I will do it. /home/htdocs/wplug needs to be a repository. All of the files in it that shouldn't be shown to the world (like the whole announcements/ dir) should be moved somewhere and symlinked back to there original location. Then in /home/htdocs/wplug run: bk bkd -pSOMEPORT -d -xcd -xpush I don't want the html and such to be in /home/www/htdocs/wplug because then the confidential repository (/home/www) would contain the other repository. Nothing good would come of that. Obviously this will require a reconfigure of apache. /home/www will contain all the config and cgi-bin stuff (and whatever else is there right now besides htdocs) and will only be available to those with accounts and ssh. The files linked from /home/htdocs/wplug (the public repository) should be in /home/www, so when we clone /home/www we have the apache configure stuff, and the private material that goes in /home/htdocs/wplug. Make sense? -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Fri Dec 22 01:46:53 2000 From: zman at angstrom.net (Zach Paine) Date: Fri, 22 Dec 2000 01:46:53 -0500 Subject: [Wplug-web] New Bk Setup: Done Message-ID: <20001222014653.A8401@angstrom.net> Well.. that was nerve racking.. I think everything is working though. wplug.org reflects the changes that were made in the previous repository. Unfortunately, the actual changesets had to be deleted. Right now anonymous access is running on port 7001 and can be grabbed via: bk clone bk://wplug.org:7001 my_dir The repository is only htdocs and below, none of the apache config stuff. Developers can grab the 'unstable' branch or the staging area via bk clone user at wplug.org:/users/zman/public_html/wplug.zman my_dir I hope to move wplug.zman to /users/zman and alias it to wplug.org/unstable What else.. oh the only files that I can think of that shouldn't be seen by joe user were in the announcements/ directory. While wplug.org/announcements functions, you will not see the directory when you grab the repository. You must have a shell account and do this: bk clone user at wplug.org:/users/zman/private And edit the files that way. They are symlinked back to /home/www/htdocs/wplug/announcements/*.* While symlinks are versioned, the content of the file is not, so changes need to be made via the private repository. Well I think everything is working now. Just need to learn a little rcs and edit the apache files so wplug.org/unstable will work. It's 1:45 and I'm very tired.. if you have any questions please ask on wplug-web at wplug.org. Once we've tested this a bit, I will post to the main list about the anonymous access. Any other files that should be hidden? -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://www.wplug.org/pipermail/wplug-web/attachments/20001222/23462bb5/attachment.bin From jeremy at gunix.net Fri Dec 22 13:27:52 2000 From: jeremy at gunix.net (Jeremy Dinsel) Date: Fri, 22 Dec 2000 10:27:52 -0800 (PST) Subject: [Wplug-web] Re: New Bk Setup: Done In-Reply-To: <20001222014653.A8401@angstrom.net> Message-ID: How are passwords sent by bk? If it is plain text, can non-system (bk only) passwords be used? If not, can bk be encapsulated in ssh or run through an stunnel? It defeats the purpose to require ssh if users will be sending their password on a daily basis. -j On Fri, 22 Dec 2000, Zach Paine wrote: : Well.. that was nerve racking.. I think everything is working though. : wplug.org reflects the changes that were made in the previous repository. : Unfortunately, the actual changesets had to be deleted. : : Right now anonymous access is running on port 7001 : and can be grabbed via: : bk clone bk://wplug.org:7001 my_dir : : The repository is only htdocs and below, none of the apache config stuff. : Developers can grab the 'unstable' branch or the staging area via : : bk clone user at wplug.org:/users/zman/public_html/wplug.zman my_dir : : I hope to move wplug.zman to /users/zman and alias it to wplug.org/unstable : : What else.. oh the only files that I can think of that shouldn't be seen by : joe user were in the announcements/ directory. While wplug.org/announcements : functions, you will not see the directory when you grab the repository. You : must have a shell account and do this: : : bk clone user at wplug.org:/users/zman/private : : And edit the files that way. They are symlinked back to : /home/www/htdocs/wplug/announcements/*.* : : While symlinks are versioned, the content of the file is not, so changes need to be made via the private repository. Well I think everything is working now. Just need to learn a little rcs and edit the apache files so wplug.org/unstable will work. It's 1:45 and I'm very tired.. if you have any questions please ask on wplug-web at wplug.org. Once we've tested this a bit, I will post to the main list about the anonymous access. : : Any other files that should be hidden? : : : -- : Zach Paine : http://www.wplug.org/~zman/zman.key : Key available from pgp.ai.mit.edu ID: 87746D3D : Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D : -- - Jeremy Dinsel - somewhere in the monkey house From zman at angstrom.net Fri Dec 22 18:07:23 2000 From: zman at angstrom.net (Zach Paine) Date: Fri, 22 Dec 2000 18:07:23 -0500 Subject: [Wplug-web] Re: New Bk Setup: Done In-Reply-To: ; from jeremy@gunix.net on Fri, Dec 22, 2000 at 10:27:52AM -0800 References: <20001222014653.A8401@angstrom.net> Message-ID: <20001222180723.C2935@angstrom.net> On Fri, Dec 22, 2000 at 10:27:52AM -0800, Jeremy Dinsel wrote: > > How are passwords sent by bk? If it is plain text, can non-system (bk only) > passwords be used? If not, can bk be encapsulated in ssh or run through an > stunnel? It defeats the purpose to require ssh if users will be sending their > password on a daily basis. > > -j Which passwords are those? Users w/ rw access send there material via ssh, so I would assume that means that everything that passes between repositories is encrypted. Anonymous users don't use any sort of authentication, but don't deal with sensitive files. -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Fri Dec 22 18:18:14 2000 From: zman at angstrom.net (Zach Paine) Date: Fri, 22 Dec 2000 18:18:14 -0500 Subject: [Wplug-web] Development Page Message-ID: <20001222181814.A3502@angstrom.net> Hey, I created a page that describes the development process for those seeking anonymous access. It is at wplug.org/~zman/wplug.zman/wplug/devel and the actual file is of course in /users/zman/public_html/wplug.zman/wplug/devel. Remember that we are using /users/zman/public_html/wplug.zman as our repository as a staging area. Little problem: Becauase of goofiness with table tags, I can't get the page to display. I know it's the table tags because I had it working earlier. Can you guys take a look at it. I have family obligations, but will work on it later tonight. -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From jeremy at gunix.net Fri Dec 22 19:37:08 2000 From: jeremy at gunix.net (Jeremy Dinsel) Date: Fri, 22 Dec 2000 16:37:08 -0800 (PST) Subject: [Wplug-web] Re: New Bk Setup: Done In-Reply-To: <20001222180723.C2935@angstrom.net> Message-ID: Perfect. -j On Fri, 22 Dec 2000, Zach Paine wrote: : On Fri, Dec 22, 2000 at 10:27:52AM -0800, Jeremy Dinsel wrote: : > : > How are passwords sent by bk? If it is plain text, can non-system (bk only) : > passwords be used? If not, can bk be encapsulated in ssh or run through an : > stunnel? It defeats the purpose to require ssh if users will be sending their : > password on a daily basis. : > : > -j : : Which passwords are those? Users w/ rw access send there material via ssh, so : I would assume that means that everything that passes between repositories is : encrypted. Anonymous users don't use any sort of authentication, but don't : deal with sensitive files. : : -- : Zach Paine : http://www.wplug.org/~zman/zman.key : Key available from pgp.ai.mit.edu ID: 87746D3D : Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D : -- - Jeremy Dinsel - somewhere in the monkey house From zman at angstrom.net Sat Dec 23 01:19:41 2000 From: zman at angstrom.net (Zach Paine) Date: Sat, 23 Dec 2000 01:19:41 -0500 Subject: [Wplug-web] Update from zman Message-ID: <20001223011941.A9396@angstrom.net> Hey, Ok, there are now a plethora of ways to view the unstable wplug website. wplug.org/~zman/wplug.zman/wplug wplug.org/unstable unstable.wplug.org all will get you there. I recommend that you all check out unstable.wplug.org/devel where you can see instructions for anonymous access and patching. The repository remains at /users/zman/public_html/wplug.zman. Later, zman -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Sat Dec 23 10:38:33 2000 From: zman at angstrom.net (Zach Paine) Date: Sat, 23 Dec 2000 10:38:33 -0500 Subject: [Wplug-web] BitKeeper patch Message-ID: This BitKeeper patch contains the following changesets: 1.25 ## Wrapped with uu ## begin 664 bkpatch13848 M(R!56YD;G,N;W)G?$-H86YG M95-E='PR,#`P,3(R,S$U,C$R-'PV-#`V-0I$(#$N,C4@,#`O,3(O,C,@,3`Z M,C0Z,S0M,#4Z,#`@>FUA;D!M871R:7 at N9'EN9&YS+F]R9R`K,B`M,`I"('IM M86Y`=W!L=6FUA;D!W<&QU9RYOFUA;D!M871R:7 at N9'EN9&YS+F]R9WQW<&QU9R]T96UP;&%T92]T M;W!\,C`P,#$R,C,Q-3(T,S1\-3DS-S,*/B!Z;6%N0&UA=')I>"YD>6YD;G,N M;W)G?'=P;'5G+V1E=F5L+VEN9&5X+G!H<'PR,#`P,3(R,C(P,S"YP:'`@/3T*>FUA;D!M871R:7 at N9'EN9&YS+F]R M9WQW<&QU9R]D979E;"]I;F1E>"YP:'!\,C`P,#$R,C(R,#,W-#E\,C,P-35\ M.#-C,#FUA;D!M871R:7 at N9'EN9&YS+F]R M9R`K-"`M-`I"('IM86Y`=W!L=66]U(&UA9&4 at 86YY M"D0U,2`Q"DDU,2`Q"@D)"3Q0/CQB/CQC96YT97(^(R!B:R!S96YD("UW=74@ M+7(Q+C0R+3$N-#@*1#4S(#$*234S(#$*"0D\4#Y);B!T:&ES(&5X86UP;&4L M('=H96X at 22!F:7)S="!U<&1A=&5D('1H92!R97!O M839D,F-C93EE,C"YD>6YD;G,N;W)G?$-H86YG > M95-E='PR,#`P,3(R,S$U,C$R-'PV-#`V-0I$(#$N,C4@,#`O,3(O,C,@,3`Z > M,C0Z,S0M,#4Z,#`@>FUA;D!M871R:7 at N9'EN9&YS+F]R9R`K,B`M,`I"('IM > M86Y`=W!L=6 M-F0R8V-E.64R-S,U.61C"D,*8R!C;&5A;FEN9R!U<"!S:&]P+ at I+(#8T,#@R > M"E`@0VAA;F=E4V5T"BTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM > M+2TM+2TM+2TM+2TM+2TM+0H*,&$P"CX@>FUA;D!W<&QU9RYO M=&5M<&QA=&4O=&]P?#(P,#`Q,C(R,#8R,3(V?#$Q,S M834Q-C$@>FUA;D!M871R:7 at N9'EN9&YS+F]R9WQW<&QU9R]T96UP;&%T92]T > M;W!\,C`P,#$R,C,Q-3(T,S1\-3DS-S,*/B!Z;6%N0&UA=')I>"YD>6YD;G,N > M;W)G?'=P;'5G+V1E=F5L+VEN9&5X+G!H<'PR,#`P,3(R,C(P,S M-7PX,V,P-S-F-S0U,&9D,#(V('IM86Y`;6%T M=6 M<&QU9R]D979E;"]I;F1E>"YP:'`@/3T*>FUA;D!M871R:7 at N9'EN9&YS+F]R > M9WQW<&QU9R]D979E;"]I;F1E>"YP:'!\,C`P,#$R,C(R,#,W-#E\,C,P-35\ > M.#-C,# M+V1E=F5L+VEN9&5X+G!H<'PR,#`P,3(R,S$U,C$R-'PU.3,T,0I$(#$N,3@@ > M,#`O,3(O,C,@,3`Z,C0Z,S0M,#4Z,#`@>FUA;D!M871R:7 at N9'EN9&YS+F]R > M9R`K-"`M-`I"('IM86Y`=W!L=6 M,C`U-'PR,C at S-'QA-F0R8V-E.64R-S,U.61C"D,*8R!!9&1E9"!S;VUE(&)E > M='1E M96PO:6YD97 at N<&AP"BTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM > M+2TM+2TM+2TM+2TM+2TM+0H*1#0U(#$*230U(#$*"0D)/%`^/&(^/&-E;G1E > M M1%]2159)4TE/3B!I6]U(&UA9&4 at 86YY > M"D0U,2`Q"DDU,2`Q"@D)"3Q0/CQB/CQC96YT97(^(R!B:R!S96YD("UW=74@ > M+7(Q+C0R+3$N-#@*1#4S(#$*234S(#$*"0D\4#Y);B!T:&ES(&5X86UP;&4L > M('=H96X at 22!F:7)S="!U<&1A=&5D('1H92!R97!O M('=P;'5G+W1E;7!L871E+W1O<"`]/0IZ;6%N0'=P;'5G+F]R9WQW<&QU9R]T > M96UP;&%T92]T;W!\,C`P,#$R,C(P-C(Q,C9\,3$S-S1\,S,R.#9A-S9B-S)A > M-3$V,0IZ;6%N0&UA=')I>"YD>6YD;G,N;W)G?'=P;'5G+W1E;7!L871E+W1O > M<'PR,#`P,3(R,S`U,#0T-WPP,# M-"TP-3HP,"!Z;6%N0&UA=')I>"YD>6YD;G,N;W)G("LP("TR"D(@>FUA;D!W > M<&QU9RYO M8V4Y93(W,S4Y9&,*0PIC(%)E;6]V960@"!5 M M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM > F+2TM"@I$,C$@, at H*(R!0871C:"!C:&5C:W-U;3UF-S$S,#4S-PH` > ` > end > _______________________________________________ > Wplug-web mailing list > Wplug-web at wplug.org > http://www.wplug.org/mailman/listinfo/wplug-web > -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Sat Dec 23 11:27:12 2000 From: zman at angstrom.net (Zach Paine) Date: Sat, 23 Dec 2000 11:27:12 -0500 Subject: [Wplug-web] Applying Patches Message-ID: <20001223112712.A14113@angstrom.net> Hey guys, I'm going out of town until Sunday night and so I figured I'd tell you know how to accept and apply patches. When we recieve a patch it will be uuencoded in the actual email. You want to either pipe the message to bk receive by hitting | in your mailer and typing the command bk receive -a /path/to/your/local/repository This will apply the patch. You can run bk changes and find out what changes were made. If you like it bk push, if not use bk changes to find the version number of the patch and bk undo -r1.3 or whatever. In some cases, people will have grabbed the source at version 1.3, then we made some aditional changes to bring it to 1.5, and they will send a patch for 1.4. I'm not sure what happens in this situation other than you have to run bk resolve to merge any conflicting file changes. Later, Zach -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://www.wplug.org/pipermail/wplug-web/attachments/20001223/54e0819f/attachment.bin From rdale at wplug.org Sun Dec 24 10:13:05 2000 From: rdale at wplug.org (Robert Dale) Date: Sun, 24 Dec 2000 10:13:05 -0500 (EST) Subject: [Wplug-web] BitKeeper patch In-Reply-To: Message-ID: On Sat, 23 Dec 2000, Zach Paine wrote: > This BitKeeper patch contains the following changesets: > 1.25 > ## Wrapped with uu ## Patches are text. It is not necessary to uuencode them. In fact, it is preferred to not encode them so one may read the changes in the email. -- Robert Dale Vive le wplug! From zman at charlie.angst-inc.com Sun Dec 24 05:28:00 2000 From: zman at charlie.angst-inc.com (zman at charlie.angst-inc.com) Date: Sun, 24 Dec 2000 10:28 +0000 Subject: [Wplug-web] BitKeeper patch Message-ID: <200012241527.KAA09214@wplug.org> >From what I've read, BitKeeper suggests that uuencode so that mailers don't mangle the patch. We could change it. Zach >On Sat, 23 Dec 2000, Zach Paine wrote: > >> This BitKeeper patch contains the following changesets: >> 1.25 >> ## Wrapped with uu ## > >Patches are text. It is not necessary to uuencode them. >In fact, it is preferred to not encode them so one may read >the changes in the email. > >-- >Robert Dale > > Vive le wplug! > > > > >_______________________________________________ >Wplug-web mailing list >Wplug-web at wplug.org >http://www.wplug.org/mailman/listinfo/wplug-web ------------------- http://duploweb.com FREE Web hosting! From jeremy at gunix.net Sun Dec 24 13:11:08 2000 From: jeremy at gunix.net (Jeremy Dinsel) Date: Sun, 24 Dec 2000 10:11:08 -0800 Subject: [Wplug-web] BitKeeper patch Message-ID: <200012241811.eBOIB8215412@joshua.gunix.net> This BitKeeper patch contains the following changesets: 1.1 ## Wrapped with uu ## begin 664 bkpatch15407 M(R!5FUA;D!W<&QU9RYO MFUA;D!W<&QU9RYOFUA;D!W<&QU9RYO6]U6]U2!IFUA;D!W<&QU9RYO2!T M;R!O<&5N(&QO9V=I;F<@*'=H:6-H('EO=2!M87D@;F]T"B,@=V%N="DL('=E M('=I;&P at 8V]N=&%C="!T:&ES(&5M86EL(&%D9')E6]N92!E;'-E(&%T('EO=7(@;&]C M871I;VX at 869T97(@.3`@9&%Y3H@"G-T871E.B`* M<&]S=&%L.B`*8V]U;G1R>3H@"G!H;VYE.B`*8V5L;#H@"G!A9V5R.B`*(R`* M(R!"=7-I;F5S"`Q-C$*5B`S"@IZ;6%N0'=P;'5G+F]R9WQ":71+965P97(O971C M+VEG;F]R97PR,#`P,3(R,C`V,C`U-'PR-#@R.'PU.#=C9&8Q,#$W.6$R86-C M"D0@,2XP(#`P+S$R+S(R(#`Q.C(P.C4T+3`U.C`P('IM86Y`=W!L=6FUA;D!W<&QU9RYO#@P"BTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM M+2TM+2TM+0H*"GIM86Y`=W!L=6FUA;D!W<&QU9RYO+RH*"B, at 4&%T8V@@8VAE8VMS=6T]9#9A86,V-V8* ` end From zman at angstrom.net Mon Dec 25 00:05:53 2000 From: zman at angstrom.net (Zach Paine) Date: Mon, 25 Dec 2000 00:05:53 -0500 Subject: [Wplug-web] The Future Message-ID: <20001225000553.A1741@angstrom.net> Hey, I figured we should start talking about where to go from here. This is what I would like to see happen on the site: 1. A new design and color scheme... it's time for a change 2. Entirely php'ized. Each page calls a few functions, all we have to write is the content of the page. What do you guys think? zman -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://www.wplug.org/pipermail/wplug-web/attachments/20001225/928e1318/attachment.bin From rdale at wplug.org Mon Dec 25 10:26:29 2000 From: rdale at wplug.org (Robert Dale) Date: Mon, 25 Dec 2000 10:26:29 -0500 (EST) Subject: [Wplug-web] The Future In-Reply-To: <20001225000553.A1741@angstrom.net> Message-ID: On Mon, 25 Dec 2000, Zach Paine wrote: > I figured we should start talking about where to go from here. This > is what I would like to see happen on the site: > > 1. A new design and color scheme... it's time for a change > 2. Entirely php'ized. Each page calls a few functions, all we have to > write is the content of the page. > > What do you guys think? 1. The website should be skinnable. Anyone could make theme. Take a look at phpThemes - http://sourceforge.net/projects/phpthemes - (which we used in RIMPS - http://sourceforge.net/projects/rimps) 2. Whee.. PHP. I don't care which language it is in now. However, it would be to our advantage if all data were stored in xml or a database. -- Robert Dale Vive le wplug! From zman at angstrom.net Mon Dec 25 12:10:35 2000 From: zman at angstrom.net (Zach Paine) Date: Mon, 25 Dec 2000 12:10:35 -0500 Subject: [Wplug-web] The Future In-Reply-To: ; from rdale@wplug.org on Mon, Dec 25, 2000 at 10:26:29AM -0500 References: <20001225000553.A1741@angstrom.net> Message-ID: <20001225121035.A625@angstrom.net> On Mon, Dec 25, 2000 at 10:26:29AM -0500, Robert Dale wrote: > 1. The website should be skinnable. Anyone could make theme. Take a look at > phpThemes - http://sourceforge.net/projects/phpthemes - (which we used in > RIMPS - http://sourceforge.net/projects/rimps) This is true. Skinable meaning different color basically right? We still need to have a basic design. > > 2. Whee.. PHP. I don't care which language it is in now. However, it > would be to our advantage if all data were stored in xml or a database. > Php is good :) As far as xml, I know nothing about it, but if you say it would benefit us, then use it :) -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From jeremy at gunix.net Mon Dec 25 17:18:56 2000 From: jeremy at gunix.net (Jeremy Dinsel) Date: Mon, 25 Dec 2000 14:18:56 -0800 Subject: [Wplug-web] BitKeeper patch Message-ID: <200012252218.eBPMIus17211@joshua.gunix.net> This BitKeeper patch contains the following changesets: 1.28 # User: jeremy # Host: joshua.gunix.net # Root: /usr/src/wplug/wplug.web # Patch vers: 1.3 # Patch type: REGULAR == ChangeSet == zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc zman at matrix.dyndns.org|ChangeSet|20001223162910|64068 D 1.28 00/12/25 14:14:25-08:00 jeremy at joshua.gunix.net +2 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C c robots.txt Added changes to keep new mail archives out of search engines K 65073 P ChangeSet ------------------------------------------------ 0a0 > zman at wplug.org|wplug/robots.txt|20001222062126|27474|8f4e5c83d9c3765a jeremy at joshua.gunix.net|wplug/robots.txt|20001224180926|06318 > zman at wplug.org|BitKeeper/etc/logging_ok|20001222062129|33812|6eac9a942d3f94f8 jeremy at joshua.gunix.net|BitKeeper/etc/logging_ok|20001225221425|06044 == BitKeeper/etc/logging_ok == zman at wplug.org|BitKeeper/etc/logging_ok|20001222062129|33812|6eac9a942d3f94f8 zman at matrix.dyndns.org|BitKeeper/etc/logging_ok|20001222203842|03694 D 1.3 00/12/25 14:14:25-08:00 jeremy at joshua.gunix.net +1 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C c Logging to logging at openlogging.org accepted K 6044 O -rw-rw-r-- P BitKeeper/etc/logging_ok ------------------------------------------------ I2 1 jeremy at joshua.gunix.net == wplug/robots.txt == zman at wplug.org|wplug/robots.txt|20001222062126|27474|8f4e5c83d9c3765a zman at wplug.org|wplug/robots.txt|20001222062127|04377 D 1.2 00/12/24 10:09:26-08:00 jeremy at joshua.gunix.net +1 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C c Added changes to keep new mail archives out of search engines K 6318 O -rw-rw-r-- P wplug/robots.txt ------------------------------------------------ I1 1 Disallow: /pipermail # Patch checksum=23b4f844 From zman at angstrom.net Mon Dec 25 17:38:33 2000 From: zman at angstrom.net (Zach Paine) Date: Mon, 25 Dec 2000 17:38:33 -0500 Subject: [Wplug-web] BitKeeper patch - Status: Applied and Pushed In-Reply-To: <200012252218.eBPMIus17211@joshua.gunix.net>; from jeremy@gunix.net on Mon, Dec 25, 2000 at 02:18:56PM -0800 References: <200012252218.eBPMIus17211@joshua.gunix.net> Message-ID: <20001225173833.B10555@angstrom.net> I applied and pushed this. Zach -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D On Mon, Dec 25, 2000 at 02:18:56PM -0800, Jeremy Dinsel wrote: > This BitKeeper patch contains the following changesets: > 1.28 > > # User: jeremy > # Host: joshua.gunix.net > # Root: /usr/src/wplug/wplug.web > > # Patch vers: 1.3 > # Patch type: REGULAR > > == ChangeSet == > zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc > zman at matrix.dyndns.org|ChangeSet|20001223162910|64068 > D 1.28 00/12/25 14:14:25-08:00 jeremy at joshua.gunix.net +2 -0 > B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc > C > c robots.txt Added changes to keep new mail archives out of search engines > K 65073 > P ChangeSet > ------------------------------------------------ > > 0a0 > > zman at wplug.org|wplug/robots.txt|20001222062126|27474|8f4e5c83d9c3765a jeremy at joshua.gunix.net|wplug/robots.txt|20001224180926|06318 > > zman at wplug.org|BitKeeper/etc/logging_ok|20001222062129|33812|6eac9a942d3f94f8 jeremy at joshua.gunix.net|BitKeeper/etc/logging_ok|20001225221425|06044 > > == BitKeeper/etc/logging_ok == > zman at wplug.org|BitKeeper/etc/logging_ok|20001222062129|33812|6eac9a942d3f94f8 > zman at matrix.dyndns.org|BitKeeper/etc/logging_ok|20001222203842|03694 > D 1.3 00/12/25 14:14:25-08:00 jeremy at joshua.gunix.net +1 -0 > B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc > C > c Logging to logging at openlogging.org accepted > K 6044 > O -rw-rw-r-- > P BitKeeper/etc/logging_ok > ------------------------------------------------ > > I2 1 > jeremy at joshua.gunix.net > > == wplug/robots.txt == > zman at wplug.org|wplug/robots.txt|20001222062126|27474|8f4e5c83d9c3765a > zman at wplug.org|wplug/robots.txt|20001222062127|04377 > D 1.2 00/12/24 10:09:26-08:00 jeremy at joshua.gunix.net +1 -0 > B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc > C > c Added changes to keep new mail archives out of search engines > K 6318 > O -rw-rw-r-- > P wplug/robots.txt > ------------------------------------------------ > > I1 1 > Disallow: /pipermail > > # Patch checksum=23b4f844 > _______________________________________________ > Wplug-web mailing list > Wplug-web at wplug.org > http://www.wplug.org/mailman/listinfo/wplug-web > From zman at angstrom.net Mon Dec 25 21:30:19 2000 From: zman at angstrom.net (Zach Paine) Date: Mon, 25 Dec 2000 21:30:19 -0500 Subject: [Wplug-web] /php Message-ID: <20001225213019.A24268@angstrom.net> What is going on with this directory? What was your intention for it? We're looking to create strongly php-based site with support for themes that the user can pick. Zach -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Mon Dec 25 21:59:56 2000 From: zman at angstrom.net (Zach Paine) Date: Mon, 25 Dec 2000 21:59:56 -0500 Subject: [Wplug-web] Publishing Message-ID: <20001225215956.B24305@angstrom.net> I would like to push the unstable repos to main one. Everything seems to be working, and I want to have /devel available directly on wplug.org. I also think it's time to move towards rob's idea of a themeable page which will also help us focus on content. I have looked at rimps and phpThemes and I think it is possible to apply phpThemes to the page, but I think we need to publish before we start messing with this. Yes/No? -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D From zman at angstrom.net Thu Dec 28 12:18:08 2000 From: zman at angstrom.net (Zach Paine) Date: Thu, 28 Dec 2000 12:18:08 -0500 Subject: [Wplug-web] Pushed unstable to stable: Done Message-ID: <20001228121808.B3103@angstrom.net> Well.. it got messy at times because of some changes that were made only to the main repos and not to any of the others, but I've sorted it out. wplug.org now has what used to be unstable, and I've introduced the beginning of theming to unstable. I uploaded all of the themes in the phpThemes package, and the config files. Now we just have to implement them :) By the way, I recommend that all of you upgrade bitkeeper to a 2.0beta version in order to avoid some problems that jeremy and I ran into. Later, Zach -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://www.wplug.org/pipermail/wplug-web/attachments/20001228/092e9264/attachment.bin From zman at angstrom.net Fri Dec 29 00:21:54 2000 From: zman at angstrom.net (Zach Paine) Date: Fri, 29 Dec 2000 00:21:54 -0500 Subject: [Wplug-web] Theme Support Message-ID: <20001229002154.A1136@angstrom.net> I've been working on themes recently. Check out unstable.wplug.org to see the ugly fruits of my labor. The point is, it works. We have a number of themes to choose from and can easily create our own. There are some problems though.. the themes involving graphics seem to get screwed up when you make tables over a certain size... take a look at the site and update your repos and see what you guys can do :) I'll keep hackin' Zach -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://www.wplug.org/pipermail/wplug-web/attachments/20001229/0eb1a257/attachment.bin From jeremy at gunix.net Fri Dec 29 02:13:55 2000 From: jeremy at gunix.net (Jeremy Dinsel) Date: Thu, 28 Dec 2000 23:13:55 -0800 Subject: [Wplug-web] BitKeeper patch Message-ID: <200012290713.XAA03372@falken.gunix.net> This BitKeeper patch contains the following changesets: 1.36 # User: jeremy # Host: falken.gunix.net # Root: /usr/src/wplug.web # Patch vers: 1.3 # Patch type: REGULAR == ChangeSet == zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc jeremy at falken.gunix.net|ChangeSet|20001229042043|36700 D 1.36 00/12/28 23:12:48-08:00 jeremy at falken.gunix.net +1 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C c TODO updated with base todo list K 36731 P ChangeSet ------------------------------------------------ 0a0 > jeremy at falken.gunix.net|TODO|20001229041859|03930|2e71a6df3049c90 jeremy at falken.gunix.net|TODO|20001229071229|23299 == TODO == jeremy at falken.gunix.net|TODO|20001229041859|03930|2e71a6df3049c90 jeremy at falken.gunix.net|TODO|20001229041900|00010 D 1.2 00/12/28 23:12:29-08:00 jeremy at falken.gunix.net +11 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C c updated with base todo list K 23299 O -rw-rw-r-- P TODO ------------------------------------------------ I1 11 Themes fun stuff: get themes all setup \ templates for future devel: base html file for users to expand upon when making new pages \ wplug/reviews: Methods for submitting, approving, deleting and updating reviews of software, books, etc \ \ \ \ # Patch checksum=07e95b34 From jeremy at gunix.net Fri Dec 29 13:59:02 2000 From: jeremy at gunix.net (Jeremy Dinsel) Date: Fri, 29 Dec 2000 10:59:02 -0800 Subject: [Wplug-web] BitKeeper patch Message-ID: <200012291859.KAA06519@falken.gunix.net> This BitKeeper patch contains the following changesets: 1.35 # User: jeremy # Host: falken.gunix.net # Root: /usr/src/wplug.web # Patch vers: 1.3 # Patch type: REGULAR == ChangeSet == zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc zman at matrix.dyndns.org|ChangeSet|20001228181515|17673 D 1.35 00/12/28 20:20:43-08:00 jeremy at falken.gunix.net +3 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C c Added files for tracking goals and projects within the project c c WISHLIST BitKeeper file /usr/src/wplug.web/WISHLIST c TODO BitKeeper file /usr/src/wplug.web/TODO K 36700 P ChangeSet ------------------------------------------------ 0a0 > jeremy at falken.gunix.net|TODO|20001229041859|03930|2e71a6df3049c90 jeremy at falken.gunix.net|TODO|20001229041900|00010 > jeremy at falken.gunix.net|WISHLIST|20001229041907|37718|812cd7bff06eed22 jeremy at falken.gunix.net|WISHLIST|20001229041908|00310 > zman at wplug.org|BitKeeper/etc/logging_ok|20001222062129|33812|6eac9a942d3f94f8 jeremy at falken.gunix.net|BitKeeper/etc/logging_ok|20001229042043|08369 == TODO == New file: TODO f x 161 V 4 jeremy at falken.gunix.net|TODO|20001229041859|03930|2e71a6df3049c90 D 1.0 00/12/28 20:18:59-08:00 jeremy at falken.gunix.net +0 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc c BitKeeper file /usr/src/wplug.web/TODO K 3930 P TODO R 2e71a6df3049c90 X 0x80 ------------------------------------------------ jeremy at falken.gunix.net|TODO|20001229041859|03930|2e71a6df3049c90 D 1.1 00/12/28 20:18:59-08:00 jeremy at falken.gunix.net +1 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C F 1 K 10 O -rw-rw-r-- P TODO ------------------------------------------------ I0 1 \ == WISHLIST == New file: WISHLIST f x 161 V 4 jeremy at falken.gunix.net|WISHLIST|20001229041907|37718|812cd7bff06eed22 D 1.0 00/12/28 20:19:07-08:00 jeremy at falken.gunix.net +0 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc c BitKeeper file /usr/src/wplug.web/WISHLIST K 37718 P WISHLIST R 812cd7bff06eed22 X 0x80 ------------------------------------------------ jeremy at falken.gunix.net|WISHLIST|20001229041907|37718|812cd7bff06eed22 D 1.1 00/12/28 20:19:07-08:00 jeremy at falken.gunix.net +0 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C F 1 K 310 O lrwxrwxrwx TODO P WISHLIST ------------------------------------------------ == BitKeeper/etc/logging_ok == zman at wplug.org|BitKeeper/etc/logging_ok|20001222062129|33812|6eac9a942d3f94f8 jeremy at joshua.gunix.net|BitKeeper/etc/logging_ok|20001225221425|06044 D 1.4 00/12/28 20:20:43-08:00 jeremy at falken.gunix.net +1 -0 B zman at wplug.org|ChangeSet|20001222062054|22834|a6d2cce9e27359dc C c Logging to logging at openlogging.org accepted K 8369 O -rw-rw-r-- P BitKeeper/etc/logging_ok ------------------------------------------------ I3 1 jeremy at falken.gunix.net # Patch checksum=16890f5b From zman at angstrom.net Sun Dec 31 13:10:21 2000 From: zman at angstrom.net (Zach Paine) Date: Sun, 31 Dec 2000 13:10:21 -0500 Subject: [Wplug-web] Include problems Message-ID: <20001231131021.A1151@angstrom.net> Hey, I've made a bunch of structural changes, including moving the template files to a diretory called lib. I'm trying to include them without specifying a full path. Check out unstable.wplug.org to see the problem. Anyone have any ideas? Zach -- Zach Paine http://www.wplug.org/~zman/zman.key Key available from pgp.ai.mit.edu ID: 87746D3D Fingerprint: B813 EFB8 ECD0 0C34 6F7F 71DD 01E9 17C3 8774 6D3D