Am Mittwoch, den 26.10.2011, 10:01 -0400 schrieb Scott Kitterman:
> On 10/26/2011 04:22 AM, Benjamin Drung wrote:
> > Am Mittwoch, den 26.10.2011, 03:07 -0500 schrieb Micah Gersten:
> >> On 10/25/2011 04:46 PM, Benjamin Drung wrote:
> >>> Am Dienstag, den 25.10.2011, 12:47 -0500 schrieb Micah Gersten:
> >>>> On 10/25/2011 07:19 AM, James Page wrote:
> >>>>> https://bugs.launchpad.net/ubuntu/+source/apcalc/+bug/880074
> >>>>> Build OK - synced from Debian testing.
> >>>>
> >>>> Until we can sponsor syncs through the LP API [1], and as long as
> >>>> there's not an immediate need for the sync, we should probably just
> >>>> subscribe ubuntu-archive, unsubcribe ubuntu-sponsors, and set to
> >>>> Confirmed once a sync is validated so that the requester can get
> >> proper
> >>>> credit for it.
> >>>
> >>> You can use sponsor-patch in oneiric, which does this job for you.
> >>
> >> I thought sponsor-patch was for patches/merges, we're talking about
> >> syncs here.
> >
> > It supports to sponsor syncs, too.
> >
> > One tool to rule them all. ;)
> 
> It's probably a somewhat archaic view, but that's not a very Unix like 
> approach to the problem.  If I was going to work on syncing a package, 
> I'd expect the tool for syncing packages to be the one I wanted to use ...

sponsor-patch is for sponsoring bugs, regardless if the bug is a sync
request, merge request, debdiff, merge proposal, or normal diff.

-- 
Benjamin Drung
Debian & Ubuntu Developer

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Reply via email to