[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: e2fsprogs_1.42.5-1.1_amd64.changes ACCEPTED into unstable



(this should probably move to -devel or somewhere)

On Sat, Mar 23, 2013 at 11:23:32AM +0000, Dmitrijs Ledkovs wrote:
> On 22 March 2013 22:17, Nicolas Boulenguez <nicolas@debian.org> wrote:
> > On Wed, Mar 20, 2013 at 09:50:07PM -0400, Theodore Ts'o wrote:
> >> >  e2fsprogs (1.42.5-1.1) unstable; urgency=low
> >> >    * Non-maintainer upload.
> >> This shouldn't have been uploaded to unstable without first getting
> >> permission from the Debian Release team (and preferably me --- it
> >> would have been nice if you had asked me before uploading the NMU)
> >
> > Sorry to be fussy, but I only suggested the patch via the BTS.
> > Dmitrijs, please put your own name into debian/changelog next time you
> > sign an NMU.
> 
> Ok, I can see how it can be confusing. who-uploads does show that it
> was my gpg signature on the upload. It's just this way I sponsor any
> other uploads were the code/changes I am not the author of. How should
> I credit the author?

There are no hard and fast rules, but conventionally:

 - if you are preparing an upload that incorporates a patch from someone
   else, thank them in the changelog:
     * Do some stuff (Closes: #n) Thanks to $person for the patch
 - if you are sponsoring a whole upload prepared by someone else, just
   sign and upload

-- 
Jonathan Wiltshire                                      jmw@debian.org
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

<directhex> i have six years of solaris sysadmin experience, from
            8->10. i am well qualified to say it is made from bonghits
			layered on top of bonghits

Attachment: signature.asc
Description: Digital signature


Reply to: