community/pipermail-archives/sup-devel/2014-01.txt (11626B) - raw
1 From ruthard.baudach@web.de Sat Jan 18 12:11:17 2014
2 From: ruthard.baudach@web.de (Ruthard Baudach)
3 Date: Sat, 18 Jan 2014 13:11:17 +0100
4 Subject: [sup-devel] remove spam label
5 Message-ID: <1390046982-sup-7856@prxbdc.dyndns.org>
6
7 Hello supppers!
8
9 I tagged some emails as spam by mistake and cannot figure out how to
10 remove this tag.
11
12 How do I do this?
13
14 Greetings,
15
16 Ruthard
17
18
19 From eric.weikl@gmx.net Sat Jan 18 13:02:10 2014
20 From: eric.weikl@gmx.net (Eric Weikl)
21 Date: Sat, 18 Jan 2014 14:02:10 +0100
22 Subject: [sup-devel] remove spam label
23 In-Reply-To: <1390046982-sup-7856@prxbdc.dyndns.org>
24 References: <1390046982-sup-7856@prxbdc.dyndns.org>
25 Message-ID: <1390050074-sup-2410@alderaan>
26
27 Hi Ruthard,
28
29 On 01/18/2014 13:11:17, Ruthard Baudach wrote:
30 > I tagged some emails as spam by mistake and cannot figure out how to
31 > remove this tag.
32 >
33 > How do I do this?
34
35 I'm not sure if this is the easiest way, but it works for me:
36
37 - search for spam mails by pressing F in your inbox, search for
38 "label:Spam"
39 - tag the ham mail(s) by pressing t for each
40 - press + to apply the next operation to all tagged mails
41 - press l to label, then enter: -spam
42 (yes, 'spam' lower-case this time)
43
44 That should remove the label from all tagged mails. I agree there should
45 be an easier way.
46
47 Hope that helps,
48 Eric
49
50 From matthieu.rakotojaona@gmail.com Sat Jan 18 14:48:10 2014
51 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
52 Date: Sat, 18 Jan 2014 15:48:10 +0100
53 Subject: [sup-devel] remove spam label
54 In-Reply-To: <1390050074-sup-2410@alderaan>
55 References: <1390046982-sup-7856@prxbdc.dyndns.org>
56 <1390050074-sup-2410@alderaan>
57 Message-ID: <1390056391-sup-5481@kpad>
58
59 Excerpts from Eric Weikl's message of 2014-01-18 14:02:10 +0100:
60 > - search for spam mails by pressing F in your inbox, search for
61 > "label:Spam"
62
63 Just for information, you can search for a label directly with L in the
64 inbox.
65
66 --
67 Matthieu Rakotojaona
68
69 From eg@gaute.vetsj.com Mon Jan 27 10:16:36 2014
70 From: eg@gaute.vetsj.com (Gaute Hope)
71 Date: Mon, 27 Jan 2014 11:16:36 +0100
72 Subject: [sup-devel] ncursesw 1.4.4 released
73 Message-ID: <1390817715-sup-212@qwerzila>
74
75 hi,
76
77 ncursesw 1.4.4 has been released. with fixes for method_missing
78 now accepting a block and working examples on ruby 1.9 and 2.0.
79
80 get it at rubygems: $ gem install ncursesw
81
82 regards, gaute
83 -------------- next part --------------
84 A non-text attachment was scrubbed...
85 Name: signature.asc
86 Type: application/pgp-signature
87 Size: 836 bytes
88 Desc: not available
89 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20140127/e0edd265/attachment.bin>
90
91 From eg@gaute.vetsj.com Mon Jan 27 10:47:48 2014
92 From: eg@gaute.vetsj.com (Gaute Hope)
93 Date: Mon, 27 Jan 2014 11:47:48 +0100
94 Subject: [sup-devel] release 0.15.3
95 Message-ID: <1390819613-sup-7922@qwerzila>
96
97 hi,
98
99 sup 0.15.3 has been released: various bugs have been fixed and the
100 (non-working) hidden_alternates option has been removed.
101
102 get it from rubygems: $ gem install sup
103
104
105 cheers, gaute
106
107
108 -------------- next part --------------
109 A non-text attachment was scrubbed...
110 Name: signature.asc
111 Type: application/pgp-signature
112 Size: 836 bytes
113 Desc: not available
114 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20140127/ce928031/attachment.bin>
115
116 From avtobiff@gmail.com Tue Jan 28 01:18:35 2014
117 From: avtobiff@gmail.com (Per Andersson)
118 Date: Tue, 28 Jan 2014 02:18:35 +0100
119 Subject: [sup-devel] Rubymail maintainership
120 Message-ID: <CABYrXSSE59VMtSg+Eze0m2P1Tx0XCN3zxVO+q3oJzgPOc4XFxw@mail.gmail.com>
121
122 Hi!
123
124 I am the Debian maintainer for sup.
125
126 Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
127 became the new upstream for that. (Instead of having a fork.)
128
129 Since a few days ago the original upstream now carries the exact same
130 functionality. Is there any reason for carrying a fork of this any longer?
131
132 I understand that the in the future a migration away from rmail is planned.
133 In the meantime, using rmail gem, could reduce complexity. Perhaps a
134 similar move as with ncursesw-ruby can be made, adopting active
135 maintainership? (I can volunteer for this!)
136
137 As Matt states, rubymail is looking for active maintainership
138
139 https://github.com/matta/rubymail/pull/2#issuecomment-33173575
140
141
142 --
143 Per
144
145 From eg@gaute.vetsj.com Tue Jan 28 07:55:50 2014
146 From: eg@gaute.vetsj.com (Gaute Hope)
147 Date: Tue, 28 Jan 2014 08:55:50 +0100
148 Subject: [sup-devel] Rubymail maintainership
149 In-Reply-To: <CABYrXSSE59VMtSg+Eze0m2P1Tx0XCN3zxVO+q3oJzgPOc4XFxw@mail.gmail.com>
150 References: <CABYrXSSE59VMtSg+Eze0m2P1Tx0XCN3zxVO+q3oJzgPOc4XFxw@mail.gmail.com>
151 Message-ID: <1390895256-sup-521@qwerzila>
152
153 Excerpts from Per Andersson's message of 2014-01-28 02:18:35 +0100:
154 > Hi!
155 >
156 > I am the Debian maintainer for sup.
157 >
158 > Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
159 > became the new upstream for that. (Instead of having a fork.)
160 >
161 > Since a few days ago the original upstream now carries the exact same
162 > functionality. Is there any reason for carrying a fork of this any longer?
163
164 Where is upstream for this, I'm not sure if I am following you? The only
165 active fork of ncurses-ruby (ncursesw-ruby) that I can find is ours -
166 which is now known as 'ncursesw' in gem world (ncursesw-sup has been
167 removed).
168
169 > I understand that the in the future a migration away from rmail is planned.
170 > In the meantime, using rmail gem, could reduce complexity. Perhaps a
171 > similar move as with ncursesw-ruby can be made, adopting active
172 > maintainership? (I can volunteer for this!)
173 >
174 > As Matt states, rubymail is looking for active maintainership
175 >
176 > https://github.com/matta/rubymail/pull/2#issuecomment-33173575
177 >
178
179 If you are up for it, that would be good, we might as well push directly
180 to RMail (and drop rmail-sup). I suggest you contact Matt and we migrate
181 the rmail-sup repoistory in sup-heliotrope (at github) to use the rmail
182 namespace. If he wants, we could also just move his repository to the
183 sup-heliotrope organization.
184
185 Please also make sure that the other maintainers of sup are
186 owners of the rmail gem so that it is not all dependant on one person.
187
188 Cheers, Gaute
189
190 -------------- next part --------------
191 A non-text attachment was scrubbed...
192 Name: signature.asc
193 Type: application/pgp-signature
194 Size: 836 bytes
195 Desc: not available
196 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20140128/6aaf0ce4/attachment.bin>
197
198 From avtobiff@gmail.com Tue Jan 28 21:21:48 2014
199 From: avtobiff@gmail.com (Per Andersson)
200 Date: Tue, 28 Jan 2014 22:21:48 +0100
201 Subject: [sup-devel] Rubymail maintainership
202 In-Reply-To: <1390895256-sup-521@qwerzila>
203 References: <CABYrXSSE59VMtSg+Eze0m2P1Tx0XCN3zxVO+q3oJzgPOc4XFxw@mail.gmail.com>
204 <1390895256-sup-521@qwerzila>
205 Message-ID: <CABYrXSRPLdBt4ba2H1qCV83-AaP4_fj0Md4QWgS_Fe58B-02UA@mail.gmail.com>
206
207 On Tue, Jan 28, 2014 at 8:55 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
208 > Excerpts from Per Andersson's message of 2014-01-28 02:18:35 +0100:
209 >> Hi!
210 >>
211 >> I am the Debian maintainer for sup.
212 >>
213 >> Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
214 >> became the new upstream for that. (Instead of having a fork.)
215 >>
216 >> Since a few days ago the original upstream now carries the exact same
217 >> functionality. Is there any reason for carrying a fork of this any longer?
218 >
219 > Where is upstream for this, I'm not sure if I am following you? The only
220 > active fork of ncurses-ruby (ncursesw-ruby) that I can find is ours -
221 > which is now known as 'ncursesw' in gem world (ncursesw-sup has been
222 > removed).
223
224 It was late when I wrote this. What I mean, but did not manage to put in
225 writing, is that the rmail-sup gem carries the same functionality. And my
226 suggestion was that we adopt active maintainership of rmail.
227
228 Sorry for the total confusion, I was tired...
229
230
231 >> I understand that the in the future a migration away from rmail is planned.
232 >> In the meantime, using rmail gem, could reduce complexity. Perhaps a
233 >> similar move as with ncursesw-ruby can be made, adopting active
234 >> maintainership? (I can volunteer for this!)
235 >>
236 >> As Matt states, rubymail is looking for active maintainership
237 >>
238 >> https://github.com/matta/rubymail/pull/2#issuecomment-33173575
239 >>
240 >
241 > If you are up for it, that would be good, we might as well push directly
242 > to RMail (and drop rmail-sup). I suggest you contact Matt and we migrate
243 > the rmail-sup repoistory in sup-heliotrope (at github) to use the rmail
244 > namespace. If he wants, we could also just move his repository to the
245 > sup-heliotrope organization.
246
247 I'll contact Matt and ask!
248
249
250 > Please also make sure that the other maintainers of sup are
251 > owners of the rmail gem so that it is not all dependant on one person.
252
253 Absolutely!
254
255
256 Best,
257 Per
258
259 From eg@gaute.vetsj.com Wed Jan 29 08:59:20 2014
260 From: eg@gaute.vetsj.com (Gaute Hope)
261 Date: Wed, 29 Jan 2014 09:59:20 +0100
262 Subject: [sup-devel] Rubymail maintainership
263 In-Reply-To: <CABYrXSRPLdBt4ba2H1qCV83-AaP4_fj0Md4QWgS_Fe58B-02UA@mail.gmail.com>
264 References: <CABYrXSSE59VMtSg+Eze0m2P1Tx0XCN3zxVO+q3oJzgPOc4XFxw@mail.gmail.com>
265 <1390895256-sup-521@qwerzila>
266 <CABYrXSRPLdBt4ba2H1qCV83-AaP4_fj0Md4QWgS_Fe58B-02UA@mail.gmail.com>
267 Message-ID: <1390985761-sup-8931@qwerzila>
268
269 Excerpts from Per Andersson's message of 2014-01-28 22:21:48 +0100:
270 > On Tue, Jan 28, 2014 at 8:55 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
271 > > Excerpts from Per Andersson's message of 2014-01-28 02:18:35 +0100:
272 > >> Hi!
273 > >>
274 > >> I am the Debian maintainer for sup.
275 > >>
276 > >> Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
277 > >> became the new upstream for that. (Instead of having a fork.)
278 > >>
279 > >> Since a few days ago the original upstream now carries the exact same
280 > >> functionality. Is there any reason for carrying a fork of this any longer?
281 > >
282 > > Where is upstream for this, I'm not sure if I am following you? The only
283 > > active fork of ncurses-ruby (ncursesw-ruby) that I can find is ours -
284 > > which is now known as 'ncursesw' in gem world (ncursesw-sup has been
285 > > removed).
286 >
287 > It was late when I wrote this. What I mean, but did not manage to put in
288 > writing, is that the rmail-sup gem carries the same functionality. And my
289 > suggestion was that we adopt active maintainership of rmail.
290 >
291 > Sorry for the total confusion, I was tired...
292 >
293 > >> I understand that the in the future a migration away from rmail is planned.
294 > >> In the meantime, using rmail gem, could reduce complexity. Perhaps a
295 > >> similar move as with ncursesw-ruby can be made, adopting active
296 > >> maintainership? (I can volunteer for this!)
297 > >>
298 > >> As Matt states, rubymail is looking for active maintainership
299 > >>
300 > >> https://github.com/matta/rubymail/pull/2#issuecomment-33173575
301 > >>
302 > >
303 > > If you are up for it, that would be good, we might as well push directly
304 > > to RMail (and drop rmail-sup). I suggest you contact Matt and we migrate
305 > > the rmail-sup repoistory in sup-heliotrope (at github) to use the rmail
306 > > namespace. If he wants, we could also just move his repository to the
307 > > sup-heliotrope organization.
308 >
309 > I'll contact Matt and ask!
310 >
311 > > Please also make sure that the other maintainers of sup are
312 > > owners of the rmail gem so that it is not all dependant on one person.
313 >
314 > Absolutely!
315
316 Sounds good! If Matt agrees to make us maintainers, but wants to retain
317 the original repo, we can just rename the rmail-sup repo to rubymail
318 and revert the gemspec changes.
319
320 - gaute
321
322 -------------- next part --------------
323 A non-text attachment was scrubbed...
324 Name: signature.asc
325 Type: application/pgp-signature
326 Size: 836 bytes
327 Desc: not available
328 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20140129/efaa15c0/attachment.bin>
329