savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[savannah-help-public] [sr #107671] Viewing Job list of multiple project


From: Karl Berry
Subject: [savannah-help-public] [sr #107671] Viewing Job list of multiple project types.
Date: Sat, 10 Aug 2013 23:03:35 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20

Follow-up Comment #12, sr #107671 (project administration):

i have not investigated the differences between the savane and savane-cleanup
repos, but i have the impression they are substantial.  as part of Sylvain's
historical effort to merge gna and savannah sources, long since abandoned on
both sides as far as i know.

i don't believe savane-cleanup is used as a live system checkout anywhere.  do
you know otherwise?  not that it would surprise me if it were; i have never
seen a comprehensible explanation of all the different savannah-related source
repos (git, cvs, bzr, others, have all been/are being used) and where they are
checked out and for what purpose, either.  this is one of the biggest barriers
to people (me, you, john, bob, anyone ...) actually working on savannah.

thus, barring other input, i confess i have a different view - my view is that
we  should recognize the reality that no one on either the gna or savannah
side is going to finish a savane merge any time in the foreseeable future. 
therefore there's no point in ever doing anything with savane-cleanup, and it
should be archived in the dust bin of history.

as for /usr/src/savane and the savane repo: certainly i agree things should be
updated in the repository, but i don't know how to tell what has been changed
or what might result from updates, so i'm always afraid to do anything.  i
mean, is the live system really running out of /usr/src/savane?  that seems
like a totally wrong directory choice for a live runtime to me. 

anyway, i just moved
frontend:/usr/src/savane/frontend/php/images/common/contexts1/people.orig.png.prev
to /root/archive on frontend, to get it out of the hier, anyway.  git status
now reports "Your branch is ahead of 'origin/master' by 9 commits." as well as
the modified people.orig.png.  Will anything bad come of pushing that? 
Doesn't seem like it.

thanks,
karl


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/support/?107671>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]