JAMES BRIAN ALLEN (ESQ).
LAW FIRM/ATTORNEY.
New London Road
Chelmsford
CM2 0AP
Hello: debian-devel@lists.debian.org;
Please treat it as a confidential and classified issue.
I'm James Allen, a government-approved Lawyer attached to Ulster Bank of London.
I'm contacting you in res
ed, but it would be useful to be able to mark changes are "package
uploader approved for upload". Possibly this could be done with PR tags
that can only be set by the package maintainer, but I think my DEP's
implementation is simpler.
--
Sean Whitton
signature.asc
Description: PGP signature
On 06/19/2017 05:37 PM, Sean Whitton wrote:
> On Mon, Jun 19, 2017 at 08:56:14AM -0400, Jeremy Bicha wrote:
>> On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton
>> wrote:
>>> Someone might contribute a fix in the form of a PR, and an uploader of
>>> the package might review that fix and determine tha
On Monday, June 19, 2017 04:37:12 PM Sean Whitton wrote:
> Hello Jeremy,
>
> On Mon, Jun 19, 2017 at 08:56:14AM -0400, Jeremy Bicha wrote:
> > On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton
wrote:
> > > Someone might contribute a fix in the form of a PR, and an uploader of
> > > the package might
Hello Jeremy,
On Mon, Jun 19, 2017 at 08:56:14AM -0400, Jeremy Bicha wrote:
> On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton
> wrote:
> > Someone might contribute a fix in the form of a PR, and an uploader of
> > the package might review that fix and determine that it should be
> > merged. They
On Mon, Jun 19, 2017 at 10:18:52AM +0100, Sean Whitton wrote:
> Hello Christian,
>
> On Sun, Jun 11, 2017 at 08:16:43PM +0100, Sean Whitton wrote:
> > Christian Seiler writes:
> >
> > > Your goal in wanting to stop people from having to deal with
> > > patch files manually is laudable, but I see
On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton wrote:
> Someone might contribute a fix in the form of a PR, and an uploader of
> the package might review that fix and determine that it should be
> merged. They then look at the master branch and decide that it should
> not go into the next upload,
Hello Christian,
On Sun, Jun 11, 2017 at 08:16:43PM +0100, Sean Whitton wrote:
> Christian Seiler writes:
>
> > Your goal in wanting to stop people from having to deal with
> > patch files manually is laudable, but I see the following way
> > forward to achieve that goal:
> >
> > - Pull request
Christian Seiler writes:
> Your goal in wanting to stop people from having to deal with
> patch files manually is laudable, but I see the following way
> forward to achieve that goal:
>
> - Pull requests.
>
> - Make it easier to create personal copies of remote (!)
>repositories in one's ow
Christian Seiler writes:
> Your goal in wanting to stop people from having to deal with
> patch files manually is laudable, but I see the following way
> forward to achieve that goal:
>
> - Pull requests.
>
> - Make it easier to create personal copies of remote (!)
>repositories in one's ow
On Sun, 11 Jun 2017, Sean Whitton wrote:
> Henrique de Moraes Holschuh writes:
>
> > Not just that. If it is for NMUs, one also has to ensure it matches
> > what got uploaded (regardless of method: NMU patch, PR, branch...).
>
> I'm not sure what you're getting at here -- this DEP is for change
On 06/11/2017 07:44 PM, Sean Whitton wrote:
> Christian Seiler writes:
>
>> To me this looks like a very complicated technical solution
>> to something that I've never encountered as a problem myself.
>
> Could you explain which parts of the proposal you find to be "very
> complicated"? Possibl
Christian Seiler writes:
> To me this looks like a very complicated technical solution
> to something that I've never encountered as a problem myself.
Could you explain which parts of the proposal you find to be "very
complicated"? Possibly I've made them seem much more complicated than
they ac
Ansgar Burchardt writes:
> What about contributions to non-packaged parts of Debian?
This DEP isn't about those -- are you saying that it ought to be
extended?
> I also don't like having more systems only a subset of contributors
> can use.
I share this concern, but it is easier for a DD to re
Henrique de Moraes Holschuh writes:
> Not just that. If it is for NMUs, one also has to ensure it matches
> what got uploaded (regardless of method: NMU patch, PR, branch...).
I'm not sure what you're getting at here -- this DEP is for changes that
*aren't* to be uploaded as part of an NMU.
--
On Fri, 09 Jun 2017, Tollef Fog Heen wrote:
> > Per the DEP:
> >
> > > it is very useful for a maintainer to know that a change has been
> > > approved by someone who has been trusted by the project with the
> > > technical ability to NMU the package
> &g
]] Sean Whitton
> Per the DEP:
>
> > it is very useful for a maintainer to know that a change has been
> > approved by someone who has been trusted by the project with the
> > technical ability to NMU the package
>
> This would be much more cumbersome to achie
Hi Sean,
Am 2017-06-07 22:56, schrieb Sean Whitton:
I am hereby reserving DEP number 15 for my draft DEP, "Reserved
namespaces for DD-approved non-maintainer changes".
I'd like to suggest discussing this DEP on d-devel (which is the
Reply-to for this e-mail). The canonical
Sean Whitton writes:
> I am hereby reserving DEP number 15 for my draft DEP, "Reserved
> namespaces for DD-approved non-maintainer changes".
>
> I'd like to suggest discussing this DEP on d-devel (which is the
> Reply-to for this e-mail). The canonical DEP text is at
Hello Jeremy,
On Wed, Jun 07, 2017 at 05:06:10PM -0400, Jeremy Bicha wrote:
> On Wed, Jun 7, 2017 at 4:56 PM, Sean Whitton wrote:
> > I am hereby reserving DEP number 15 for my draft DEP, "Reserved
> > namespaces for DD-approved non-maintainer changes".
>
>
low similar to GitHub / GitLab's fork-and-
> merge behaviour.
We also want merge requests! This DEP's implementation should live
alongside those.
Per the DEP:
> it is very useful for a maintainer to know that a change has been
> approved by someone who has been trusted by the
Sean Whitton writes ("DEP 15: Reserved namespace for DD-approved non-maintainer
changes"):
> I am hereby reserving DEP number 15 for my draft DEP, "Reserved
> namespaces for DD-approved non-maintainer changes".
>
> I'd like to suggest discussing this DEP on
在 2017年6月7日星期三 +08 下午9:56:39，Sean Whitton 写道：
> Dear all,
>
> I am hereby reserving DEP number 15 for my draft DEP, "Reserved
> namespaces for DD-approved non-maintainer changes".
>
> I'd like to suggest discussing this DEP on d-devel (which is the
> Reply-to
On Wed, Jun 7, 2017 at 4:56 PM, Sean Whitton wrote:
> I am hereby reserving DEP number 15 for my draft DEP, "Reserved
> namespaces for DD-approved non-maintainer changes".
I think this proposal somewhat contradicts DEP-14.
It also feels to me like this proposal is another way
Dear all,
I am hereby reserving DEP number 15 for my draft DEP, "Reserved
namespaces for DD-approved non-maintainer changes".
I'd like to suggest discussing this DEP on d-devel (which is the
Reply-to for this e-mail). The canonical DEP text is at
<http://dep.debian.net/
On Wed, Apr 16, 2008 at 1:34 PM, Bas Wijnen <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> On Wed, Apr 16, 2008 at 01:08:05PM +0200, Ondrej Certik wrote:
> > if I want to packge a new upstream version of DM-Upload-Allowed
> > library (for example [1]), it changes the name of the binary package
> > and
Hi,
On Wed, Apr 16, 2008 at 01:08:05PM +0200, Ondrej Certik wrote:
> if I want to packge a new upstream version of DM-Upload-Allowed
> library (for example [1]), it changes the name of the binary package
> and thus goes to NEW.
>
> Last time I asked it wasn't possible for me, as a DM, to upload i
Hi,
if I want to packge a new upstream version of DM-Upload-Allowed
library (for example [1]), it changes the name of the binary package
and thus goes to NEW.
Last time I asked it wasn't possible for me, as a DM, to upload it and
I had to search for a sponsor.
Is there some policital reason for
On Mon, Jun 27, 2005 at 09:52:36PM -0700, Don Armstrong wrote:
> On Mon, 27 Jun 2005, Colin Watson wrote:
> > On Mon, Jun 27, 2005 at 05:43:24PM +0900, Miles Bader wrote:
> > > Does anyone still use ssh1? It seems quite common for it not to be
> > > supported these days...
> >
> > One machine I us
On Mon, 27 Jun 2005, Colin Watson wrote:
> On Mon, Jun 27, 2005 at 05:43:24PM +0900, Miles Bader wrote:
> > Does anyone still use ssh1? It seems quite common for it not to be
> > supported these days...
>
> One machine I use fairly frequently as a terminal is a PowerMac
> running Mac OS 8, where k
Il giorno lun, 27/06/2005 alle 17.43 +0900, Miles Bader ha scritto:
> Lionel Elie Mamane <[EMAIL PROTECTED]> writes:
> >> Hmmm, why SSH1 and even telnet and not SSH2?
> >
> > You misread: There is NO telnet. As for SSH2, it works fine, but SSH1
> > doesn't work. Probably a typo .
>
> Does anyone
On Mon, Jun 27, 2005 at 05:43:24PM +0900, Miles Bader wrote:
> Lionel Elie Mamane <[EMAIL PROTECTED]> writes:
> > You misread: There is NO telnet. As for SSH2, it works fine, but SSH1
> > doesn't work. Probably a typo .
>
> Does anyone still use ssh1? It seems quite common for it not to be
> sup
Lionel Elie Mamane <[EMAIL PROTECTED]> writes:
>> Hmmm, why SSH1 and even telnet and not SSH2?
>
> You misread: There is NO telnet. As for SSH2, it works fine, but SSH1
> doesn't work. Probably a typo .
Does anyone still use ssh1? It seems quite common for it not to be
supported these days...
-
On Mon, 27 Jun 2005, Lionel Elie Mamane wrote:
On Mon, Jun 27, 2005 at 09:51:07AM +0200, Andreas Tille wrote:
-- Forwarded message --
Date: Mon, 27 Jun 2005 06:20:50 +
From: [EMAIL PROTECTED]
^^^
H, this sound not good for the sake of further communication.
On Mon, Jun 27, 2005 at 09:51:07AM +0200, Andreas Tille wrote:
>>-- Forwarded message --
>>Date: Mon, 27 Jun 2005 06:20:50 +
>>From: [EMAIL PROTECTED]
^^^
> H, this sound not good for the sake of further communication.
> Why not including a mail address which can
20:50 +
From: [EMAIL PROTECTED]
^^^
H, this sound not good for the sake of further communication.
Why not including a mail address which can be really used?
To: [EMAIL PROTECTED]
Subject: [ISO-8859-1] Alioth Project Approved
Your project registration for Alioth has been app
Please visit http://www.razorsearch.com/help.html for our online
support center. We are open 24 hrs a day to serve you.
Thank you,
Razor Search Team
---
*** AUTOMATIC RESPONSE ***
You will receive
This is an autoresponder. I'll never see your message.
Sanyo Customer Service has received your email. We respond to emails
Monday -Friday 7:30 AM -4:00PM central time except for holidays. Please
allow us time to serve you The products that we are associated with are
Sanyo Televisions, VCRs,DVD players and Multimedia Remotes sold through
Wal-Mart.
39 matches
Mail list logo
