[PATCH] Karmic: Change patch templates to separate sauce and

[Tim Gardner]

Amit Kucheria wrote:
> Currently, all our patches go into SAUCE. The original definition of SAUCE was
> patches that would _not_ get accepted upstream (see the template). This has been
> lost. 
> 
> This change to the templates will force us to think what patches should go
> upstream and what will be rejected.
> 
> Amit Kucheria (1):
>   UBUNTU: [Config] Changes to patch templates to separate upstream and
>     sauce
> 
>  debian/commit-templates/patch          |   28 ----------------------
>  debian/commit-templates/patch-sauce    |   40 ++++++++++++++++++++++++++++++++
>  debian/commit-templates/patch-upstream |   28 ++++++++++++++++++++++
>  debian/commit-templates/sauce-patch    |   38 ------------------------------
>  debian/commit-templates/update-configs |    7 ++++-
>  5 files changed, 73 insertions(+), 68 deletions(-)
>  delete mode 100644 debian/commit-templates/patch
>  create mode 100644 debian/commit-templates/patch-sauce
>  create mode 100644 debian/commit-templates/patch-upstream
>  delete mode 100644 debian/commit-templates/sauce-patch
> 
> 

If you use the patch-upstream template, do we delay pushing to our core
repo until its been accepted by an upstream maintainer? What if its
rejected? Perhaps we should keep a branch of pending upstream patch
submissions that don't get moved into our mainline until they've been
accepted upstream. (I know Stefan wanted more process...)

On a more finicky note, can you change the patch template names so that
tab completion works on the first unique character? upstream-patch
instead of patch-upstream, config-update instead of update-configs, etc.

rtg
-- 
Tim Gardner tim.gardner at canonical.com