I think something along these lines is a good idea.
There are things about falsifying the reply-to: that can get ugly and
unpredictable, but what if we did this:
* Simply have the svn system send commits to the sisuite-devel list.
I would think that we really want everyone on the devel list to see all
the commits. We're more likely to get good feedback and better code
review that way.
Comments? In particular from everyone on the -devel list...
-Brian
Thus spake Bernard Li ([EMAIL PROTECTED]):
May I suggest we change the "reply-to:" for systemimager-commits to
sisuite-devel? :-)
Cheers,
Bernard
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Brian Elliott Finley
Sent: Wednesday, December 21, 2005 9:55
To: Andrea Righi
Cc: [EMAIL PROTECTED]
Subject: Re: [Systemimager-commits] r3342 - trunk/etc
Better yet, is there any reason not to source the functions prior to
sourcing the variables?
-Brian
Thus spake Andrea Righi ([EMAIL PROTECTED]):
>Author: arighi
>Date: 2005-12-21 14:41:18 -0600 (Wed, 21 Dec 2005)
>New Revision: 3342
>
>Modified:
> trunk/etc/autoinstallscript.template
>Log:
>- shellout function is not available in /tmp/variables.txt sourcing
>- display "Imaging completed" message in virtual console at
the end of the installation
>
>
>Modified: trunk/etc/autoinstallscript.template
>===================================================================
>--- trunk/etc/autoinstallscript.template 2005-12-20
20:18:51 UTC (rev 3341)
>+++ trunk/etc/autoinstallscript.template 2005-12-21
20:41:18 UTC (rev 3342)
>@@ -19,7 +19,7 @@
> # via /tmp/variables.txt. Apparently the shell we use in
BOEL is not
> # intelligent enough to take a "set -a" parameter.
> #
>-. /tmp/variables.txt || shellout
>+. /tmp/variables.txt
>
> # Load functions and other variables
> . /etc/init.d/functions
>@@ -387,6 +387,7 @@
> # Tell the image server we're done
> #
> rsync $IMAGESERVER::scripts/imaging_complete > /dev/null 2>&1
>+logmsg "Imaging completed"
> #
>
##############################################################
##################
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep
through log files
>for problems? Stop! Download the new AJAX search engine that makes
>searching your log files as easy as surfing the web.
DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>systemimager-commits mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/systemimager-commits
--
Brian Elliott Finley
Mobile: 630.631.6621
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep
through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web.
DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
systemimager-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/systemimager-commits
--
Brian Elliott Finley
Mobile: 630.631.6621
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
