This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "theslinux-buildsystem". The branch, _utils has been updated via 93b2ae98007d4b38d20ea1396d7e3ce58641012e (commit) from f710b5be65753c7b62dff7db1fa86bb674a61464 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 93b2ae98007d4b38d20ea1396d7e3ce58641012e Author: Ky-Anh Huynh <kyanh@xxxxxxxxxxxxx> Date: Sat Aug 10 08:30:12 2013 +0700 + FIXME: split huge script into parts By doing this we may lost history entries of some functions (they are still there, but need effort to locate them). We did work without a good design, right? No problem. Until now we still do not what we should do. Some intial packages * Core packages (_s_env) * Making packages * Process PKGBUILDs * Calculate dependencies ----------------------------------------------------------------------- Summary of changes: _utils/run.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/_utils/run.sh b/_utils/run.sh index a00c8bb..0008760 100755 --- a/_utils/run.sh +++ b/_utils/run.sh @@ -5,6 +5,7 @@ # License: GPL v2 (http://www.gnu.org/licenses/gpl-2.0.html) # Date : 2013 March 30th # Home : https://github.com/TheSLinux/buildsystem/tree/_utils +# FIXME : Split this huge Bash script into parts (libraries) # # Copyright (c) 2013 Anh K. Huynh <kyanh@xxxxxxxxxxxxx> # hooks/post-receive -- theslinux-buildsystem -- Purpose: Store commits, feeds from other projects Post: mailto:theslinux-phantom@xxxxxxxxxxxxx Archive, Gmane: http://theslinux.org/lists/phantom/ Subscribe: mailto:theslinux-phantom-request@xxxxxxxxxxxxx?Subject=subscribe Unsubscribe: mailto:theslinux-phantom-request@xxxxxxxxxxxxx?Subject=unsubscribe Other information: http://theslinux.org/lists (vi) or http://theslinux.org/lists/en (en) Support: mailto:theslinux-questions@xxxxxxxxxxxxx