Talk:Mailing lists: Difference between revisions
m (Johan G moved page Talk:Mailing list to Talk:Mailing lists: Plural form) |
(Headings: Capital first letter; New section: Bug reports on mailing lists?) |
||
Line 1: | Line 1: | ||
== Template for mailing list URLs == | == Template for mailing list URLs == | ||
we should set up a template for the rows in the table, so that we can easily reuse/localize everything elsewhere (as per the git/repo link templates) | we should set up a template for the rows in the table, so that we can easily reuse/localize everything elsewhere (as per the git/repo link templates) | ||
* address | * address | ||
Line 11: | Line 10: | ||
--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 10:58, 20 April 2015 (EDT) | --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 10:58, 20 April 2015 (EDT) | ||
== | == Additional info == | ||
{{FGCquote | {{FGCquote | ||
|One additional thing to keep in mind is that our flightgear-commitlogs<br/> | |One additional thing to keep in mind is that our flightgear-commitlogs<br/> | ||
Line 70: | Line 68: | ||
}} | }} | ||
}} | }} | ||
== Bug reports on mailing lists? == | |||
Is not that bad advice? Should not bug reports be redirected to the {{tickets|issue tracker}} in order to lessen unproductive/disruptive noise, in particular on the developer mailing list? | |||
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:50, 10 May 2015 (EDT) |
Revision as of 20:50, 10 May 2015
Template for mailing list URLs
we should set up a template for the rows in the table, so that we can easily reuse/localize everything elsewhere (as per the git/repo link templates)
- address
- archives
- subscribe
- comments
- description (localized)
- status
--Hooray (talk) 10:58, 20 April 2015 (EDT)
Additional info
One additional thing to keep in mind is that our flightgear-commitlogs mailing list has a maximum message size configured to 160Kb. Messages — Curtis Olson (2015-04-19). Re: [Flightgear-devel] [Flightgear-commitlogs] [FGData] FlightGear
data - next generation branch next updated.
7b595eca19e1bfb83ae330c02f2eeec5e9c9da58.
(powered by Instant-Cquotes) |
Both the post-commit-email and git-multimail scripts have an option for this (hooks.emailmaxlines and — Edward d'Auvergne (2015-04-19). Re: [Flightgear-devel] [Flightgear-commitlogs] [FGData] FlightGear
data - next generation branch next updated.
7b595eca19e1bfb83ae330c02f2eeec5e9c9da58.
(powered by Instant-Cquotes) |
The default mailman option is 40kb, so we have doubled the allowable size twice now. :-) I don't have a big emotional attachment to the current — Curtis Olson (2015-04-19). Re: [Flightgear-devel] [Flightgear-commitlogs] [FGData] FlightGear
data - next generation branch next updated.
7b595eca19e1bfb83ae330c02f2eeec5e9c9da58.
(powered by Instant-Cquotes) |
Bug reports on mailing lists?
Is not that bad advice? Should not bug reports be redirected to the issue tracker in order to lessen unproductive/disruptive noise, in particular on the developer mailing list?