GNU bug report logs - #71924
31.0.50; elpa.gnu.org has misleading link to bbdb source code

Previous Next

To reply to this bug, email your comments to 71924 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jules Tamagnan <jtamagnan <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 31.0.50; elpa.gnu.org has misleading link to bbdb source code
Date: Wed, 03 Jul 2024 11:06:47 -0700

---

* Background

This might be expected but I found it a bit confusing so figured I would
open a bug report in case it is not expected.

The high level issue is that it seems like the elpa website is pointing
to the wrong version of the bbdb source code.

* Problem

The `bbdb` package is defined in elpa as pulling from nongnu elpa. This
can be seen here -
https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/elpa-packages?h=main#n89

However the link to `bbdb`'s source code from the elpa website
(http://elpa.gnu.org/packages/bbdb.html) points to the gnu elpa version
of the source code:
https://git.savannah.gnu.org/cgit/emacs/elpa.git/?h=externals/bbdb.

This causes confusion because the website does not point to the true
source code that would be installed.

This further causes confusion because both versions of `bbdb` are
extremely different notably the elpa version of bbdb contains a
`bbdb-site.el` file
(https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/lisp/bbdb-site.el?h=externals/bbdb)
whereas the non-gnu elpa version contains a `bbdb-site.el.in` file
(https://git.savannah.nongnu.org/cgit/bbdb.git/tree/lisp/bbdb-site.el.in)

* Desired solutions

1. The elpa website should link to the bbdb source code that is defined
   in elpa-packages.
2. Both versions of the elpa source code:
   https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
   https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.

I'd be willing to tackle solution 1 and possibly solution 2 but it isn't
clear to me where the source code for the elpa website is such that it
can be modified to point to the expected URL. It also isn't clear to me
if we should be keeping both versions of the source code or consolidate
since it seems like the version on gnu.org is no longer in use.

Best,
Jules

---

In GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.42, cairo version 1.18.0)
Repository revision: 9cb2a2040888c28587bed2b0902d9da90720f9a0
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101013
System Description: NixOS 24.11 (Vicuna)

Message #8 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Jeremy Bryant <jb <at> jeremybryant.net>
To: Jules Tamagnan <jtamagnan <at> gmail.com>
Cc: Philip Kaludercic <philipk <at> posteo.net>, 71924 <at> debbugs.gnu.org
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Sat, 13 Jul 2024 22:46:38 +0100

Jules Tamagnan <jtamagnan <at> gmail.com> writes:

> ---
>
> * Background
>
> This might be expected but I found it a bit confusing so figured I would
> open a bug report in case it is not expected.
>
> The high level issue is that it seems like the elpa website is pointing
> to the wrong version of the bbdb source code.
>
> * Problem
>
> The `bbdb` package is defined in elpa as pulling from nongnu elpa. This
> can be seen here -
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/elpa-packages?h=main#n89
>
> However the link to `bbdb`'s source code from the elpa website
> (http://elpa.gnu.org/packages/bbdb.html) points to the gnu elpa version
> of the source code:
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/?h=externals/bbdb.
>
> This causes confusion because the website does not point to the true
> source code that would be installed.
>
> This further causes confusion because both versions of `bbdb` are
> extremely different notably the elpa version of bbdb contains a
> `bbdb-site.el` file
> (https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/lisp/bbdb-site.el?h=externals/bbdb)
> whereas the non-gnu elpa version contains a `bbdb-site.el.in` file
> (https://git.savannah.nongnu.org/cgit/bbdb.git/tree/lisp/bbdb-site.el.in)
>
> * Desired solutions
>
> 1. The elpa website should link to the bbdb source code that is defined
>    in elpa-packages.
> 2. Both versions of the elpa source code:
>    https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
>    https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.
>
> I'd be willing to tackle solution 1 and possibly solution 2 but it isn't
> clear to me where the source code for the elpa website is such that it
> can be modified to point to the expected URL. It also isn't clear to me
> if we should be keeping both versions of the source code or consolidate
> since it seems like the version on gnu.org is no longer in use.
>
> Best,
> Jules
>
> ---
>
> In GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
> 3.24.42, cairo version 1.18.0)
> Repository revision: 9cb2a2040888c28587bed2b0902d9da90720f9a0
> Repository branch: master
> Windowing system distributor 'The X.Org Foundation', version 11.0.12101013
> System Description: NixOS 24.11 (Vicuna)

Adding Philip to this report

Message #11 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Jules Tamagnan <jtamagnan <at> gmail.com>
To: Jeremy Bryant <jb <at> jeremybryant.net>
Cc: Philip Kaludercic <philipk <at> posteo.net>, 71924 <at> debbugs.gnu.org
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Wed, 24 Jul 2024 13:31:04 -0700

Jeremy Bryant <jb <at> jeremybryant.net> writes:

> Adding Philip to this report

Brilliant, thank you. Let me know if there is anything I can do to help
this along. I'm happy to take on fixes but am unsure how to make the
proper modifications to the ELPA website and unsure how we should go
about reconciling the differences between the versions:
 - Should we remove the non-gnu version and improve the gnu version?
 - Should we remove the gnu version and use exclusively the non-gnu
    version?
 - Should we keep both but have the source be the same?

Best,
Jules

Message #14 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Philip Kaludercic <philipk <at> posteo.net>
To: Jules Tamagnan <jtamagnan <at> gmail.com>
Cc: 71924 <at> debbugs.gnu.org
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Sun, 28 Jul 2024 11:59:02 +0000

Jules Tamagnan <jtamagnan <at> gmail.com> writes:

> ---
>
> * Background
>
> This might be expected but I found it a bit confusing so figured I would
> open a bug report in case it is not expected.
>
> The high level issue is that it seems like the elpa website is pointing
> to the wrong version of the bbdb source code.
>
> * Problem
>
> The `bbdb` package is defined in elpa as pulling from nongnu elpa. This
> can be seen here -
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/elpa-packages?h=main#n89
>
> However the link to `bbdb`'s source code from the elpa website
> (http://elpa.gnu.org/packages/bbdb.html) points to the gnu elpa version
> of the source code:
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/?h=externals/bbdb.
>
> This causes confusion because the website does not point to the true
> source code that would be installed.
>
> This further causes confusion because both versions of `bbdb` are
> extremely different notably the elpa version of bbdb contains a
> `bbdb-site.el` file
> (https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/lisp/bbdb-site.el?h=externals/bbdb)
> whereas the non-gnu elpa version contains a `bbdb-site.el.in` file
> (https://git.savannah.nongnu.org/cgit/bbdb.git/tree/lisp/bbdb-site.el.in)
>
> * Desired solutions
>
> 1. The elpa website should link to the bbdb source code that is defined
>    in elpa-packages.

ELPA always mirrors the remote repositories, and links to this mirror,
but you can set the URL in the package header to point to whatever site
you like.

> 2. Both versions of the elpa source code:
>    https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
>    https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.

If you merge the elpa branch into your branch and then adjust what you
want, it should go through.

> I'd be willing to tackle solution 1 and possibly solution 2 but it isn't
> clear to me where the source code for the elpa website is such that it
> can be modified to point to the expected URL. It also isn't clear to me
> if we should be keeping both versions of the source code or consolidate
> since it seems like the version on gnu.org is no longer in use.

> Best,
> Jules
>
> ---
>
> In GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
> 3.24.42, cairo version 1.18.0)
> Repository revision: 9cb2a2040888c28587bed2b0902d9da90720f9a0
> Repository branch: master
> Windowing system distributor 'The X.Org Foundation', version 11.0.12101013
> System Description: NixOS 24.11 (Vicuna)
>
>
>
>

Jeremy Bryant <jb <at> jeremybryant.net> writes:

> Jules Tamagnan <jtamagnan <at> gmail.com> writes:
>
>> ---
>>
>> * Background
>>
>> This might be expected but I found it a bit confusing so figured I would
>> open a bug report in case it is not expected.
>>
>> The high level issue is that it seems like the elpa website is pointing
>> to the wrong version of the bbdb source code.
>>
>> * Problem
>>
>> The `bbdb` package is defined in elpa as pulling from nongnu elpa. This
>> can be seen here -
>> https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/elpa-packages?h=main#n89
>>
>> However the link to `bbdb`'s source code from the elpa website
>> (http://elpa.gnu.org/packages/bbdb.html) points to the gnu elpa version
>> of the source code:
>> https://git.savannah.gnu.org/cgit/emacs/elpa.git/?h=externals/bbdb.
>>
>> This causes confusion because the website does not point to the true
>> source code that would be installed.
>>
>> This further causes confusion because both versions of `bbdb` are
>> extremely different notably the elpa version of bbdb contains a
>> `bbdb-site.el` file
>> (https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/lisp/bbdb-site.el?h=externals/bbdb)
>> whereas the non-gnu elpa version contains a `bbdb-site.el.in` file
>> (https://git.savannah.nongnu.org/cgit/bbdb.git/tree/lisp/bbdb-site.el.in)
>>
>> * Desired solutions
>>
>> 1. The elpa website should link to the bbdb source code that is defined
>>    in elpa-packages.
>> 2. Both versions of the elpa source code:
>>    https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
>>    https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.
>>
>> I'd be willing to tackle solution 1 and possibly solution 2 but it isn't
>> clear to me where the source code for the elpa website is such that it
>> can be modified to point to the expected URL. It also isn't clear to me
>> if we should be keeping both versions of the source code or consolidate
>> since it seems like the version on gnu.org is no longer in use.
>>
>> Best,
>> Jules
>>
>> ---
>>
>> In GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
>> 3.24.42, cairo version 1.18.0)
>> Repository revision: 9cb2a2040888c28587bed2b0902d9da90720f9a0
>> Repository branch: master
>> Windowing system distributor 'The X.Org Foundation', version 11.0.12101013
>> System Description: NixOS 24.11 (Vicuna)
>
> Adding Philip to this report
>
>
>
>

Jules Tamagnan <jtamagnan <at> gmail.com> writes:

> Jeremy Bryant <jb <at> jeremybryant.net> writes:
>
>> Adding Philip to this report
>
> Brilliant, thank you. Let me know if there is anything I can do to help
> this along. I'm happy to take on fixes but am unsure how to make the
> proper modifications to the ELPA website and unsure how we should go
> about reconciling the differences between the versions:
>  - Should we remove the non-gnu version and improve the gnu version?

FWIW this is also an option, but I think we can avoid this.

>  - Should we remove the gnu version and use exclusively the non-gnu
>     version?
>  - Should we keep both but have the source be the same?

I'd vote for this one.

> Best,
> Jules
>
>
>
>

-- 
	Philip Kaludercic on peregrine

Message #17 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: 71924 <at> debbugs.gnu.org, Jules Tamagnan <jtamagnan <at> gmail.com>
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Fri, 28 Feb 2025 17:47:18 -0800

Philip Kaludercic <philipk <at> posteo.net> writes:

>> * Desired solutions
>>
>> 1. The elpa website should link to the bbdb source code that is defined
>>    in elpa-packages.
>
> ELPA always mirrors the remote repositories, and links to this mirror,
> but you can set the URL in the package header to point to whatever site
> you like.
>
>> 2. Both versions of the elpa source code:
>>    https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
>>    https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.
>
> If you merge the elpa branch into your branch and then adjust what you
> want, it should go through.

Does that answer all questions here, or is there more to do here?

Message #24 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Philip Kaludercic <philipk <at> posteo.net>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: 71924 <at> debbugs.gnu.org, Jules Tamagnan <jtamagnan <at> gmail.com>
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Thu, 06 Mar 2025 18:46:17 +0000

Stefan Kangas <stefankangas <at> gmail.com> writes:

> Philip Kaludercic <philipk <at> posteo.net> writes:
>
>>> * Desired solutions
>>>
>>> 1. The elpa website should link to the bbdb source code that is defined
>>>    in elpa-packages.
>>
>> ELPA always mirrors the remote repositories, and links to this mirror,
>> but you can set the URL in the package header to point to whatever site
>> you like.
>>
>>> 2. Both versions of the elpa source code:
>>>    https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
>>>    https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.
>>
>> If you merge the elpa branch into your branch and then adjust what you
>> want, it should go through.
>
> Does that answer all questions here, or is there more to do here?

As far as I see the ELPA branch has been merged upstream, but hasn't
been synchronised yet?

Message #27 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: 71924 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>,
 Jules Tamagnan <jtamagnan <at> gmail.com>
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Sat, 8 Mar 2025 10:03:45 +0000

Philip Kaludercic <philipk <at> posteo.net> writes:

> Stefan Kangas <stefankangas <at> gmail.com> writes:
>
>> Philip Kaludercic <philipk <at> posteo.net> writes:
>>
>>>> * Desired solutions
>>>>
>>>> 1. The elpa website should link to the bbdb source code that is defined
>>>>    in elpa-packages.
>>>
>>> ELPA always mirrors the remote repositories, and links to this mirror,
>>> but you can set the URL in the package header to point to whatever site
>>> you like.
>>>
>>>> 2. Both versions of the elpa source code:
>>>>    https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
>>>>    https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.
>>>
>>> If you merge the elpa branch into your branch and then adjust what you
>>> want, it should go through.
>>
>> Does that answer all questions here, or is there more to do here?
>
> As far as I see the ELPA branch has been merged upstream, but hasn't
> been synchronised yet?

Stefan, any comments here?

Message #30 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Jules Tamagnan <jtamagnan <at> gmail.com>
Cc: Philip Kaludercic <philipk <at> posteo.net>, 71924 <at> debbugs.gnu.org,
 Roland Winkler <winkler <at> gnu.org>
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Sat, 08 Mar 2025 14:27:33 -0500

Hi Jules,

> * Problem
>
> The `bbdb` package is defined in elpa as pulling from nongnu elpa.
> This can be seen here -
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/elpa-packages?h=main#n89

Not exactly: it's pulling from the "nongnu.org" part of Savannah because
it is hosted and developed there (instead of, say, Codeberg).
I.e. BBDB is a "nongnu package" in the sense that, while it's hosted
on infrastructure provided by the GNU project, it is not officially part
of the GNU project (contrary to Emacs, say).

That's not to be confused with NonGNU ELPA, which is a distribution site
for Emacs packages.  The two are related, admittedly.  Also since all
packages distributed via GNU ELPA (such as BBDB) are considered as being
"somewhat part of Emacs", that means BBDB is both a "nongnu
project" and "part of a GNU project".
In practice, this doesn't matter very much.

> However the link to `bbdb`'s source code from the elpa website
> (http://elpa.gnu.org/packages/bbdb.html) points to the gnu elpa version
> of the source code:
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/?h=externals/bbdb.

And that's the right link in the sense that this is the code used to
build the tarball that's distributed on GNU ELPA.

> This causes confusion because the website does not point to the true
> source code that would be installed.

The code over at `nongnu.org` is closely related, and is indeed the
"upstream" of the code in `elpa.git`, but is not exactly "the true
source code that would be installed".

Clearly, the current setup is not ideal.  It's the result of the usual
historical accidents.  It would be desirable to fix it by
aligning/merging the `nongnu.org` code and the `elpa.git` code, e.g. so
that `elpa.gnu.org` can automatically pull changes from `nongnu.org`
rather than relying on explicit pushes by BBDB's maintainers.

But it also comes with its downsides (e.g. extra work in the short
term), which is why we settled on this setup.  This said, time has
passed and maybe the tradeoffs have changed now (AUCTeX was using
a similar organization for similar historical reasons and has recently
bit the bullet), so it's probably a good idea to take another look
at it.

Roland, what do you think?


        Stefan

Message #33 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Roland Winkler <winkler <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Philip Kaludercic <philipk <at> posteo.net>, 71924 <at> debbugs.gnu.org,
 Jules Tamagnan <jtamagnan <at> gmail.com>
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Sun, 09 Mar 2025 18:49:42 -0500

On Sat, Mar 08 2025, Stefan Monnier wrote:
> Roland, what do you think?

Stefan, I think you have given a fair account from what I can tell.
When BBDB became available via GNU Elpa, part of the reason to keep BBDB
also at savannah was that back then this simplified packaging BBDB for
debian (and maybe also other distros).  But the BBDB maintainer for
debian has confirmed to me that for debian this is no issue anymore.
Debian can package BBDB either way.  And yes, it will certainly simplify
development and maintenance of BBDB if there is only one "official
source" for it (at GNU Elpa).  So I have asked on the BBDB mailing list
whether there are still any reasons to also have the BBDB repository at
NonGNU Savannah or whether this repository can be put to rest.  I do not
expect to receive serious objections, but you never know.  I'll wait
some time so that others can respond.

(I assume nothing at Savannah needs to be deleted for this.  The git
repository documents the history of BBDB since the early days of BBDB.
But one can put a note that development of BBDB now only happens at GNU
Elpa.)

Message #36 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Roland Winkler <winkler <at> gnu.org>
Cc: Philip Kaludercic <philipk <at> posteo.net>, 71924 <at> debbugs.gnu.org,
 Jules Tamagnan <jtamagnan <at> gmail.com>
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Sun, 09 Mar 2025 22:35:07 -0400

>> Roland, what do you think?
>
> Stefan, I think you have given a fair account from what I can tell.
> When BBDB became available via GNU Elpa, part of the reason to keep BBDB
> also at savannah was that back then this simplified packaging BBDB for
> debian (and maybe also other distros).  But the BBDB maintainer for
> debian has confirmed to me that for debian this is no issue anymore.
> Debian can package BBDB either way.  And yes, it will certainly simplify
> development and maintenance of BBDB if there is only one "official
> source" for it (at GNU Elpa).

[ That matches AUCTeX's experience.  ]

> So I have asked on the BBDB mailing list
> whether there are still any reasons to also have the BBDB repository at
> NonGNU Savannah or whether this repository can be put to rest.  I do not
> expect to receive serious objections, but you never know.  I'll wait
> some time so that others can respond.
>
> (I assume nothing at Savannah needs to be deleted for this.  The git
> repository documents the history of BBDB since the early days of BBDB.
> But one can put a note that development of BBDB now only happens at GNU
> Elpa.)

Note that the development could still very well happen over at the
`nongnu.git` repository instead of `elpa.git`.  The main issue is the
*content* of the branch on which development takes place.  Currently the
content over at `nongnu.git` is not appropriate for GNU ELPA, which is
why you have to first "massage" it and then push it to `elpa.git`.
But if you changed that content to match what GNU ELPA needs, then GNU
ELPA could automatically track the code over at `nongnu.git` and you
could keep doing the development over there.

The main difference between the two scenarios is one of administrative
hurdles (e.g. you can easily add/remove commit rights to contributors over
at the `nongnu.git` whereas only Emacs maintainers can do that on
`elpa.git`).

In any case, let me know if there's something I can do to help,


        Stefan

Message #39 received at 71924 <at> debbugs.gnu.org (full text, mbox):

From: Roland Winkler <winkler <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Philip Kaludercic <philipk <at> posteo.net>, 71924 <at> debbugs.gnu.org,
 Jules Tamagnan <jtamagnan <at> gmail.com>
Subject: Re: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb
 source code
Date: Tue, 11 Mar 2025 14:18:39 -0500

On Sun, Mar 09 2025, Stefan Monnier wrote:
> Note that the development could still very well happen over at the
> `nongnu.git` repository instead of `elpa.git`.  The main issue is the
> *content* of the branch on which development takes place.  Currently the
> content over at `nongnu.git` is not appropriate for GNU ELPA, which is
> why you have to first "massage" it and then push it to `elpa.git`.
> But if you changed that content to match what GNU ELPA needs, then GNU
> ELPA could automatically track the code over at `nongnu.git` and you
> could keep doing the development over there.

Sounds good to me!

> The main difference between the two scenarios is one of administrative
> hurdles (e.g. you can easily add/remove commit rights to contributors
> over at the `nongnu.git` whereas only Emacs maintainers can do that on
> `elpa.git`).

This has rarely happened.  But it is obviously no disadvantage.

Also, this will certainly imply if anyone finds BBDB on savannah in
whatever way cannot be fooled by an outdated repository.

> In any case, let me know if there's something I can do to help,

Thanks, I may come back to this.  I am not an expert with git.  But I
assume it will be possible to rearrange things on savannah such that
the history of files that are kept is preserved.

Roland

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.