[sr #110621] request better handling of numbered-list markup in email

2022-04-21 Thread Dave
Follow-up Comment #5, sr #110621 (project administration): Numbering still works in email generated from a Rich Markup post originating on savannah.nongnu.org (the condition that was previously shown to work in comment #2): http://lists.gnu.org/r/savannah-hackers/2022-04/msg00029.html So this doe

[sr #110621] request better handling of numbered-list markup in email

2022-04-21 Thread Dave
Follow-up Comment #4, sr #110621 (project administration): This change appears to have been undone since then; compare: 1. http://savannah.gnu.org/bugs/?62344#comment0 2. http://lists.gnu.org/r/bug-groff/2022-04/msg00052.html I've made those into a numbered list in this post to see if the proble

Re: Please make a repo for the GNU C Manual

2022-04-21 Thread Ineiev
On Thu, Apr 21, 2022 at 12:22:17AM -0400, Richard Stallman wrote: > > Is it something completely different? > > Yes, totally, and enormously better. From this one, you can actually > learn C. > > > We should treat them as two different works. But how? > > We could call this repo something d

[sr #110640] Sign-up email went missing

2022-04-21 Thread Ineiev
Update of sr #110640 (project administration): Assigned to:None => ineiev ___ Follow-up Comment #1: I've just activated your account manually; please confirm that you can login. _

Re: Please make a repo for the GNU C Manual

2022-04-21 Thread Alfred M. Szmidt
How about reusing the gnu-c-manual Savannah project; the old gnu-c-manual git repository is then renamed to gnu-c-reference-manual or old-gnu-c-manual. And put the new GNU C book into gnu-c-manual or whatever title the book will have.