[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-devel
Subject:    Re: Bug#340428: octave2.9 - lists mailing list as uploader in changelog
From:       Rafael Laboissiere <rafael () debian ! org>
Date:       2005-11-25 8:01:24
Message-ID: 20051125080124.GA24179 () laboiss2
[Download RAW message or body]

* Bastian Blank <waldi@debian.org> [2005-11-24 23:45]:

> On Thu, Nov 24, 2005 at 10:48:39PM +0100, Rafael Laboissiere wrote:
> > Yes, I have been doing things wrongly in the past, but this is not the
> > case anymore.  The Changed-By fields are correct now.  See, for instance,
> > my last upload:
> >     http://lists.debian.org/debian-devel-changes/2005/11/msg01728.html
> [upload of octave2.9_2.9.4-7]
> 
> | Maintainer: Debian/IA64 Build Daemon <buildd@caballero...>
> | Changed-By: Debian Octave Group <pkg-octave-devel@lists...>

Could you please explain to me why having Changed-By as a mailing list in
this case (a binary NMU done by an autobuilder) is problematic?  You may
have good reasons for thinking Change-By should list a real person , but
I fail to understand it.

Notice that I am not religious about this ML versus person issue in the
debian/changelog entry.  If the majority of developers think we should do
one way or the other, I will comply with the decision and do the
necessary changes at the DOG (the Debian Octave Group, in case you did
not yet get the acronym).  I would like just to understand the rationale,
though.
 
-- 
Rafael


-- 
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

[prev in list] [next in list] [prev in thread] [next in thread]