[sr #110378] request Git repo set up for GNU Superopt

Update of sr #110378 (project administration): Status: In Progress => Done Open/Closed:Open => Closed ___ Follow-up Comment #10: Sorry for t

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #9, sr #110378 (project administration): Sorry for the long delay in response. I intend the 'p' branch to be the default one. How do i set that up? ___ Reply to this item at:

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #8, sr #110378 (project administration): Ping? Has there been an update on the git repository for GNU Superopt? I look and I still see the same problem now as before. It has an "archive" branch and a "p" branch but neither of those match the default clone branch. Adding to my

[sr #110378] request Git repo set up for GNU Superopt

Update of sr #110378 (project administration): Assigned to: ineiev => rwp ___ Reply to this item at: __

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #7, sr #110378 (project administration): > Thanks. Everything is fine, now, w/ these instructions. Great! Good to hear that things are better. And I see that code has been pushed. However I also see that there is a problem that needs to be fixed. There are only two branches

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #6, sr #110378 (project administration): > Let us know if this works for you. Thanks. Everything is fine, now, w/ these instructions. > There is additional documentation in the > https://savannah.nongnu.org/maintenance/UsingGit/ page. Strangely enough, i used instructions on

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #5, sr #110378 (project administration): Since you have a git repository for your source all you need to do is to push it and publish it to Savannah git repository. Let's assume you want "origin" to be Savannah. In that case delete any previous origin and set it again. Or choo

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #4, sr #110378 (project administration): Sorry, i guess i'm still not being clear. Here's the situation: GNU Superopt was developed and maintained in the 1990s, long before savannah was set up. It went unmaintained until a few years ago, when i volunteered to take over maintena

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #3, sr #110378 (project administration): Your question catches me really confused. If you are the maintainer then I think I can't be faulted for expecting that you would be the best person to know where the source code to the package you are maintaining resides! And if you don'

[sr #110378] request Git repo set up for GNU Superopt

Follow-up Comment #2, sr #110378 (project administration): Sorry, i was not clear earlier. There is no current CVS repo to convert (AFAICT). I tried following the instructions anyway and saw: $ LANG=C git cvsimport -A ../.authors.txt -p x -v -d:ext:t...@cvs.savannah.gnu.org:/sources/superopt sup

[sr #110378] request Git repo set up for GNU Superopt

Update of sr #110378 (project administration): Status:None => In Progress Assigned to:None => ineiev ___ Follow-up Comment #1: Enable Git o

[sr #110378] request Git repo set up for GNU Superopt

URL: Summary: request Git repo set up for GNU Superopt Project: Savannah Administration Submitted by: ttn Submitted on: Tue 17 Nov 2020 03:07:43 AM CET Category: Source code re