[Top][All Lists]

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

Re: [Savannah-hackers-public] Allowing git repos to automatically push t

From: Daniel Katz
Subject: Re: [Savannah-hackers-public] Allowing git repos to automatically push to$PROJECT
Date: Thu, 22 Jul 2021 17:24:18 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Icedove/78.11.0

Thank you for responding! Seeing the curl commands used makes the
script make a lot more sense now.

I've been thinking about how the workflow for creating git repos for
updating software subpages on should be and how those repos can
best be identified by wildebeest for syncing.

If it's possible project maintainers to create arbitrary repos under
their project, I think that they should be responsible for creating a
sub repo called "web." The project maintainer should also email someone
(me most likely) to add their project name to a text file which
identifies that they want their subpage to be gotten
via git instead of CVS. The text file should likely be somewhere on
Savannah and be accessible via the web. This proposal shouldn't require
any source code modifications or even creating a new subdomain.

For example, Emacs has its source repo, GNU ELPA, NonGNU ELPA, and Emacs
Org mode git repos on its project page. If the maintainers wanted it to
have a git repo for it's subpage instead of CVS, a maintainer should
create a repo called web (which would reside at
"") and then email me to add
Emacs to the aforementioned text file.

I'm willing to maintain this text file past my internship (might be a
great way to get more involved with Savannah in general).

Also, I saw that there is a script to generate documentation for each
project. I think it runs on the Savannah side of things but want to confirm.

On 7/21/21 5:48 PM, Karl Berry wrote:
> Hi Daniel,
>     I'm also wondering if anyone knows of or has access to the CVS
>     hook/script that is on Savannah?
> A gnu example is vcs1:/srv/cvs/web/emacs/CVSROOT/loginfo, which contains:
> #<savane>
> ALL echo 'Triggering webpages update...'; cat > /dev/null; curl 
> -s -F type=gnu -F 
> project=`basename %r`
> #</savane>
> A nongnu example (type=non-gnu instead of gnu, otherwise the same):
> $ cat /srv/cvs/web/zutils/CVSROOT
> #<savane>
> ALL echo 'Triggering webpages update...'; cat > /dev/null; curl 
> -s -F type=non-gnu -F 
> project=`basename %r`
> #</savane>
> We wrote a few words about this in the sv wiki:
> We (sv people) have never seen the script or had access to what
> happens on the fsf side, but I guess you do.
>     I plan to modify the scripts to work with both Git and CVS 
> Nice. Certainly a long-requested feature. Besides the changes on the fsf
> side, it also requires some changes to Savannah to support git as an
> option for web repositories. If you were planning to work on that too,
> that's great. I don't know that any of the current sv volunteers have
> any available time for it (I don't, sadly enough).
> Hope this helps,
> Karl

reply via email to

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