[arch-dev-public] [PATCH 4/7] Remove testing2* scripts

Eric Bélanger snowmaniscool at gmail.com
Fri Mar 12 00:15:39 CET 2010

On Thu, Mar 11, 2010 at 6:07 PM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On Thu, Mar 11, 2010 at 5:00 PM, Eric Bélanger <snowmaniscool at gmail.com> wrote:
>> On Thu, Mar 11, 2010 at 5:13 PM, Daniel J Griffiths (Ghost1227)
>> <ghost1227 at archlinux.us> wrote:
>>> On 03/11/10 at 04:06pm, Dan McGee wrote:
>>>> On Thu, Mar 11, 2010 at 4:03 PM, Ghost1227 <ghost1227 at archlinux.us> wrote:
>>>> > ---
>>>> Why do none of your patches have commit messages outside of the
>>>> subject? Why are these getting removed? What is the new command? How,
>>>> 6 months from now, am I going to make sense of this commit?
>>>> Sorry for sounding like I'm coming down with a hammer on your patches
>>>> here, but I think this things are truly important.
>>>> -Dan
>>> Not a problem, the commit messages (with the exception of the first)
>>> are taken directly from the commit messages on Aaron's dbscripts branch.
>>> The testing2* scripts are being removed because the db-move script
>>> can now handle multiple packages in any repo natively.
>>> --
>> What would be the new command to move packages out of testing?
> db-move has always been the workhorse here. db-move just did the extra
> steps of allowing multiple packages specified AND figuring out the
> target repo.
> This patch covers the first case, but not the later

Personnally, I would prefer keeping the testing2* scripts.  They are
more convenient (especially with tab completion) than using db-move
directly with all its arguments.

More information about the arch-dev-public mailing list