mainSavannah Administration - Support: sr #111027, Create a gnubg-nn git repository


sr #111027: Create a gnubg-nn git repository

Submitter:  Philippe Michel <plm>
Submitted:  Fri 01 Mar 2024 10:23:46 PM UTC
Category:  Additional Git repositories Priority:  5 - Normal
Severity:  3 - Normal Status:  Ready For Test
Privacy:  Public Assigned to:  carlc
Operating System:  None Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Thu 07 Mar 2024 05:15:12 AM UTC, comment #5: 

> rather that a separate mailing list, are there internal aliases or lists

corresponding to the project group admins or the bug tracker global list?

There are not.

We could hard code in a list of addresses.  And it is not difficult to edit those later.

But mailing lists are pretty much without any cost incrementally.  We have some 1500+ mailing lists already and incrementally adding another one is not a burden.  Therefore it's the thing we reach for most often.

Bob Proulx <rwp>
Site Administrator
Tue 05 Mar 2024 10:16:50 PM UTC, comment #4: 

Regarding addresses that could be used in notifications, rather that a separate mailing list, are there internal aliases or lists
corresponding to the project group admins or the bug tracker global list? If this is the case, are there reasons not to use one of them?

Philippe Michel <plm>
Sat 02 Mar 2024 05:32:37 PM UTC, comment #3: 

Normally we don't block access to the CVS repository as it is often needed again.  Often people find that they did a conversion with an error and need to do it again.  Sometimes people have need to look back into the previous repository.

If you wish to redirect people who checkout the cvs repository then I suggest deleting all of the files from there and committing only a README file that redirects them.  That's best.  Because then you can redirect them from the old repository to the new repository.

Normally the commits or diffs mailing list would contain the output of a hook which emails the commitdiff of the commit.  It is the result of installing a hook script.  As to what the script might do the script might do anything that one wants it to do.  And therefore it's a little hard to answer the question of what commit notification email might be sent because it might be anything that one could program and that could be almost anything.

I might suggest the emacs diffs hook using the git_multimail program as being a typical example.  It's a 3rd party project.  And there are other commitdiff notification programs and configurations available too.

You said you looked at other commit notification lists and therefore I am sure you noticed that there are different notification styles in use.  If you liked one of them more than another we would happily clone the configuration of that one for you.

Bob Proulx <rwp>
Site Administrator
Sat 02 Mar 2024 04:49:34 PM UTC, comment #2: 

Thanks for your diligence. I was able to push the converted repository without difficulties.

You can disable commits in the gnubg CVS repository (the CvsDisabling page says nothing about checkouts and updates: will they display some kind of notice or continue silently?)

Regarding automated emails, I'm not sure what to do at this stage. I see that some projects have a ...-commits mailing list, and looked at the archive of one of them. Is it the kind of information that would be sent: not just the commit message and a short reference to the change but the entire diff ?

Philippe Michel <plm>
Sat 02 Mar 2024 06:03:06 AM UTC, comment #1: 

Hi Philippe Michel

I have created the gnubg-nn repository; it's currently empty so you will get a warning when cloning it.

I see it on the list of git repositories, here:

You can edit the description here:

If you'd like automated emails after push let me know the list/address and I can get that going, also.   Let me know anything else I might look at and, of course, if anything doesn't doesn't work as expected.


Corwin Brust <carlc>
Site Administrator
Fri 01 Mar 2024 10:23:46 PM UTC, original submission:  

We juste migrated the gnubg project repository from CVS to git and found it useful to split it in two:
- gnubg for the main project
- gnubg-nn for ancillary tools, of interest to a much smaller audience.

Would you mind creating this second repository under the gnubg project with RW access for the same accounts ?

Philippe Michel <plm>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by rwp (Posted a comment)
  • -email is unavailable- added by carlc (Updated the item)
  • -email is unavailable- added by plm (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-03-02 carlc StatusIn Progress Ready For Test
    2024-03-02 carlc StatusNone In Progress
        Assigned toNone carlc

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code