[Savannah-help-public] Who are these past savannah hackers?

Hi all, GNU AUCTeX will eventually drop CVS in favour of some modern dVCS. Right now, I'm experimenting with converting the CVS repository to bzr and git. Thereby, I also transform the commit history to show the real committer names as it's common nowadays. However, there are some committer name

Re: [Savannah-help-public] Who are these past savannah hackers?

"Michael J. Flickinger" writes: Hi Michael and Alfred, > Two of these accounts exist on Savannah: > > ++---+ > | realname | user_name | > ++---+ > | Pavel Jan?k| pj| > | Werner LEMBERG | wl| > ++---

[savannah-help-public] [sr #108308] Please enable git commit notifications for auctex

URL: Summary: Please enable git commit notifications for auctex Project: Savannah Administration Submitted by: tsdh Submitted on: Fri 31 May 2013 01:17:25 PM CEST Category: None

[savannah-help-public] [sr #108308] Please enable git commit notifications for auctex

Follow-up Comment #2, sr #108308 (project administration): Hi Michael, then please send the full diffs+commits mails to auctex-di...@gnu.org. What do you use for the notifications? Git comes with a script /usr/share/git/contrib/hooks/post-receive-email that can be used for that purpose. De

[savannah-help-public] [sr #108308] Please enable git commit notifications for auctex

Follow-up Comment #4, sr #108308 (project administration): Hi John, the auctex-commit archives at http://lists.gnu.org/archive/html/auctex-commit/ still only show the latest commits that were done before moving to Git. And since your comment, I've done some commits/pushes (yesterday), but those

[savannah-help-public] [sr #108308] Please enable git commit notifications for auctex

Follow-up Comment #6, sr #108308 (project administration): Hi John, indeed, the spam filter was configured in a way that discarded any message that doesn't match the old CVS commit messages. I've adapted that to the new Git commit messages, and now they make it to the list. One remaining proble

[savannah-help-public] [sr #108308] Please enable git commit notifications for auctex

Follow-up Comment #8, sr #108308 (project administration): Thanks! ___ Reply to this item at: ___ Message sent via/by Savannah http://savannah.gnu

[savannah-help-public] [sr #108409] Make the old GNU AUCTeX CVS repository read-only

URL: Summary: Make the old GNU AUCTeX CVS repository read-only Project: Savannah Administration Submitted by: tsdh Submitted on: Mon 07 Oct 2013 03:20:55 PM CEST Category: Develope

[savannah-help-public] [sr #108409] Make the old GNU AUCTeX CVS repository read-only

Follow-up Comment #2, sr #108409 (project administration): Hi Bob, it seems to work. When trying to commit a change, now I get: /sources/auctex/auctex/THIS_REPOSITORY_IS_OBSOLETE.txt,v <-- THIS_REPOSITORY_IS_OBSOLETE.txt new revision: 1.2; previous revision: 1.1 cvs [commit aborted]: could not

[savannah-help-public] [sr #108411] Enable commit mails including diffs for GNU AUCTeX

URL: Summary: Enable commit mails including diffs for GNU AUCTeX Project: Savannah Administration Submitted by: tsdh Submitted on: Tue 08 Oct 2013 02:42:37 PM CEST Category: Develo

[savannah-help-public] [sr #108409] Make the old GNU AUCTeX CVS repository read-only

Follow-up Comment #4, sr #108409 (project administration): Hey Bob, the commitinfo script is very nice. Now I get this output: This repository is obsolete and marked read-only to prevent commits. The sources have been moved to another repository. Please contact the developers for more informati

[savannah-help-public] [sr #108411] Enable commit mails including diffs for GNU AUCTeX

Follow-up Comment #2, sr #108411 (project administration): Hi Bob, indeed we want the want the latter solution, that is, short commit mails to auctex-commit and full diffs to auctex-diffs, so two post-receive-email hook scripts are needed with different values of hooks.mailinglist and hooks.showr

[savannah-help-public] [sr #108411] Enable commit mails including diffs for GNU AUCTeX

Follow-up Comment #5, sr #108411 (project administration): Hi Bob. I've just committed and pushed some changes, and I can confirm that the setup now works as requested. Thanks a lot! Feel free to close the request. ___ Reply to this item

[savannah-help-public] [sr #109625] Mail to t...@gnu.org is not delivered anymore

BS8J0afCKw37YquYp+zf9mpju97YZ7xasTl59hQ5UpeD7cDvW27QA= X-Received: by 2002:a9d:3a0a:: with SMTP id j10mr5868459otc.229.1547654364789; Wed, 16 Jan 2019 07:59:24 -0800 (PST) MIME-Version: 1.0 From: Tassilo Horn Date: Wed, 16 Jan 2019 16:59:15 +0100 Message-ID: Subject: Gmail to gnu To: Tassilo Ho

[savannah-help-public] [sr #109625] Mail to t...@gnu.org is not delivered anymore

Follow-up Comment #1, sr #109625 (project administration): Apparently, I just received the confirmation of this issue correctly delivered to my GNU address... So it seems like I cannot send mail to t...@gnu.org via my Gmail account. And it seems like others have this problem, too. For example,

[savannah-help-public] [sr #109625] Mail to t...@gnu.org is not delivered anymore

Follow-up Comment #2, sr #109625 (project administration): Ok, now I've also tried sending mail to t...@gnu.org from my wife's Gmail and GMX accounts, and for both of them, I get the bounce mails. ___ Reply to this item at:

[savannah-help-public] [sr #109625] Mail to t...@gnu.org is not delivered anymore

Follow-up Comment #3, sr #109625 (project administration): I've asked Robert if he also got that error mail when sending his reply to me, and that's what he said. He probably knew what went wrong: Yes, I got that exact error, plus i just got "relay not permitted" for Eli. I suspect fencepost.gnu

[sr #110614] auctex-diffs emails should be in the same format as emacs-diffs

URL: Summary: auctex-diffs emails should be in the same format as emacs-diffs Project: Savannah Administration Submitted by: tsdh Submitted on: Thu 24 Feb 2022 09:17:00 PM CET

[sr #110614] auctex-diffs emails should be in the same format as emacs-diffs

Follow-up Comment #2, sr #110614 (project administration): Thanks for the response, Bob. There's no need to hurry here. It just occurred to us after having the setup we have for many years that spawning a new discussion on auctex-devel initiated by a diff mail results in a suboptimal thread subjec

[sr #110614] auctex-diffs emails should be in the same format as emacs-diffs

Follow-up Comment #4, sr #110614 (project administration): Hi Bob, there seems to be some misconfiguration still. The last push by Arash resulted in this output: -> git push Enumerating objects: 7, done. Counting objects: 100% (7/7), done. Delta compression using up to 8 threads Compressing ob

[sr #110614] auctex-diffs emails should be in the same format as emacs-diffs

Follow-up Comment #5, sr #110614 (project administration): Reading your docs, shouldn't it be mailingList (with capital L) instead of mailinglist? And maybe commitList would even be more appropriate for the auctex-diffs, i.e., one mail with diff per commit instead of one diff mail per ref-change/

[sr #110614] auctex-diffs emails should be in the same format as emacs-diffs

Follow-up Comment #8, sr #110614 (project administration): Hi Bob, the mails are much better now. We only have these minor additional requests: 1. Could the Subject prefix [AUCTeX-diffs] be removed? emacs-diffs doesn't have it, too. 2. Could the From: header be set to the commit author's addre

[sr #111096] Unprotect the auctex master branch (and protect main)

Open/Closed: Open Discussion Lock: Any ___ Follow-up Comments: --- Date: Fri 26 Jul 2024 07:16:47 AM CEST By: Tassilo Horn We auctex developers have new "main" branch as

[sr #111096] Unprotect the auctex master branch (and protect main)

Follow-up Comment #2, sr #111096 (group administration): Thanks Bob, that was quick! ___ Reply to this item at: ___ Message sent via Savannah htt