Re: intent to hijack python-paramiko

To: debian developers <debian-devel@lists.debian.org>, 344734@bugs.debian.org, jbouse@debian.org
Subject: Re: intent to hijack python-paramiko
From: Martin Michlmayr <tbm@cyrius.com>
Date: Mon, 17 Jul 2006 21:21:30 +0200
Message-id: <[🔎] 20060717192130.GA24076@deprecation.cyrius.com>
In-reply-to: <[🔎] 20060717183514.GD6015@larstiq.dyndns.org>
References: <[🔎] 20060717173557.GA30294@piper.madduck.net> <[🔎] 20060717174037.GC21626@deprecation.cyrius.com> <[🔎] 20060717183514.GD6015@larstiq.dyndns.org>

* Wouter van Heyst <larstiq@larstiq.dyndns.org> [2006-07-17 20:35]:
> > He was moving cross-country in May, so I suggest you NMU for now.
> 
> Would NMUing a new upstream be ok in this instance then?

I think so, yes.
-- 
Martin Michlmayr
http://www.cyrius.com/

Reply to:

Follow-Ups:
- Re: intent to hijack python-paramiko
  - From: "Jeremy Bouse" <jtbouse@gmail.com>

References:
- intent to hijack python-paramiko
  - From: martin f krafft <madduck@debian.org>
- Re: intent to hijack python-paramiko
  - From: Martin Michlmayr <tbm@cyrius.com>
- Re: intent to hijack python-paramiko
  - From: Wouter van Heyst <larstiq@larstiq.dyndns.org>

Prev by Date: Re: Bits from the Package Tracking System
Next by Date: Re: greylisting on debian.org?
Previous by thread: Re: intent to hijack python-paramiko
Next by thread: Re: intent to hijack python-paramiko
Index(es):
- Date
- Thread