[PATCH] [HARDY] [SAUCE] Allow insertchanges to work in later version chroots
Tim Gardner
tim.gardner at canonical.com
Fri Mar 4 13:59:59 UTC 2011
On 03/03/2011 03:34 PM, Steve Conklin wrote:
> This is a very minor change which only affects one maintenance script.
> No changes to kernel code.
>
> The command "git-log" was used in the script, which prevented the
> insertchanges target from executing unless you were in a hardy chroot.
>
> This changes that to "git log". I have confirmed that it still works in
> a hardy chroot, and it also now works in a Lucid chroot.
>
> Signed-off-by: Steve Conklin<sconklin at canonical.com>
> ---
> debian/rules.d/1-maintainer.mk | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/debian/rules.d/1-maintainer.mk
> b/debian/rules.d/1-maintainer.mk
> index 4625252..d088596 100644
> --- a/debian/rules.d/1-maintainer.mk
> +++ b/debian/rules.d/1-maintainer.mk
> @@ -66,7 +66,7 @@ endif
> @echo "CONCURRENCY_LEVEL = $(CONCURRENCY_LEVEL)"
>
> printchanges:
> - @git-log Ubuntu-$(release)-$(prev_revision)..HEAD | \
> + @git log Ubuntu-$(release)-$(prev_revision)..HEAD | \
> perl -w -f debian/scripts/misc/git-ubuntu-log $(ubuntu_log_opts)
>
> insertchanges:
>
applied
--
Tim Gardner tim.gardner at canonical.com
More information about the kernel-team
mailing list