Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-08-22 Thread Sean Whitton
Dear Nicholas, On Mon, Aug 21 2017, Nicholas D Steeves wrote: > Would you like me to add this to the documentation? Of course I'll > also submit a patch upstream. Would be nice. > Also, please let me know if you're currently too busy to sponsor this > one. I can find an off-team sponsor if

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-08-21 Thread Nicholas D Steeves
Hi, On Fri, Jul 07, 2017 at 09:20:03PM -0400, Nicholas D Steeves wrote: > On Tue, Jun 13, 2017 at 06:42:28PM +0100, Sean Whitton wrote: > > Hello Nicholas, > > > > On Mon, Jun 12, 2017 at 07:33:12PM -0400, Nicholas D Steeves wrote: > > > Would it be better to ship README.org and file a bug

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-07-07 Thread Nicholas D Steeves
Hi Sean, On Tue, Jun 13, 2017 at 06:42:28PM +0100, Sean Whitton wrote: > Hello Nicholas, > > On Mon, Jun 12, 2017 at 07:33:12PM -0400, Nicholas D Steeves wrote: > > Would it be better to ship README.org and file a bug against the > > package myself? > > Yes. Why not ship README.org in the

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-06-14 Thread Sean Whitton
Hello Nicholas, On Tue, Jun 13, 2017 at 09:39:43PM -0400, Nicholas D Steeves wrote: > Phase four: Do you think that it would be useful to have > d/package.convert-to-info, d/package.convert-to-text, etc? This would > allow a plain d/rules. This probably wouldn't work because each conversion

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-06-13 Thread Nicholas D Steeves
Hi Sean, On Tue, Jun 13, 2017 at 06:42:28PM +0100, Sean Whitton wrote: > Hello Nicholas, > > On Mon, Jun 12, 2017 at 07:33:12PM -0400, Nicholas D Steeves wrote: > > Would it be better to ship README.org and file a bug against the > > package myself? > > Yes. Why not ship README.org in the

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-06-13 Thread Sean Whitton
Hello Nicholas, On Mon, Jun 12, 2017 at 07:33:12PM -0400, Nicholas D Steeves wrote: > Would it be better to ship README.org and file a bug against the > package myself? Yes. Why not ship README.org in the interim? > I still don't have a plan for Policy 12.4, and am currently wondering > if

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-06-12 Thread Nicholas D Steeves
On Mon, Jun 12, 2017 at 02:13:02PM +0100, Sean Whitton wrote: > Hello, > > On Sun, Jun 11 2017, Nicholas D Steeves wrote: > > > I am looking for a sponsor for my package "rich-minority" > > > > Package name : rich-minority Version : 1.0.1-1 > > Here's a review of

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-06-12 Thread Sean Whitton
Hello, On Sun, Jun 11 2017, Nicholas D Steeves wrote: > I am looking for a sponsor for my package "rich-minority" > > Package name : rich-minority Version : 1.0.1-1 Here's a review of bc58ab0a49df6002e4e034cea8c1398fd7407322: - why not just install README.org as it is? - the file is not

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-06-11 Thread Nicholas D Steeves
I decided to change this one to experimental rather than unstable and have pushed the changes and reuploaded to mentors. Rationale: I haven't tested smart-mode-line extensively enough with emacs25. signature.asc Description: Digital signature

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-06-11 Thread Nicholas D Steeves
Package: sponsorship-requests Severity: wishlist Control: block 864393 by -1 Dear mentors, I am looking for a sponsor for my package "rich-minority" Package name: rich-minority Version : 1.0.1-1 Upstream Author : Artur Malabarba URL :