Mailinglist Archive: opensuse-buildservice (349 mails)

< Previous Next >
Re: [opensuse-buildservice] osc rdiff (was Re: Novell ID's for OSC Plugins)
  • From: "Dr. Peter Poeml" <poeml@xxxxxxx>
  • Date: Thu, 29 Nov 2007 18:25:45 +0100
  • Message-id: <20071129172545.GZ30003@xxxxxxx>
On Thu, Nov 29, 2007 at 05:52:24PM +0100, Dr. Peter Poeml wrote:
On Thu, Nov 29, 2007 at 05:39:21PM +0100, Adrian Schröter wrote:
On Thursday 29 November 2007 17:21:43 wrote Dr. Peter Poeml:
On Thu, Nov 29, 2007 at 01:33:47PM +0100, Adrian Schröter wrote:


an equivalent for cvs rdiff would work without any checked out sources,

osc rdiff <TO_PROJECT> <TO_PACKAGE> [--package <FROM_PACKAGE>]
[--project <FROM_PROJECT>]

It'd also need options for revision and orevision.

How about

osc rdiff [-rN[:M]] [[--oldprj OLD_PROJECT] --oldpkg OLD_PACKAGE]]

looks even better to me :)

One should note that the result is a "pretty diff", which goes into tar
balls and is handy for reviews -- not a normal diff which yields an
appliable patch.

hm, maybe even default to "--project openSUSE:Factory" if no argument is
given ...

Maybe a good idea...

While experimenting, I noticed that
returns a non-empty diff, even though package=opackage and

Is this a diff to the last revision? It looks like that.

I hacked up an rdiff command, and committed it to svn.

I hope it works as expected.

The default behaviour, if opackage and oproject are not specified, is a
diff against the last revision -- not against Factory. So it behaves
similar like the backend.

The patch is also applied to the package tracking branch.

"WARNING: This bug is visible to non-employees. Please be respectful!"

SUSE LINUX Products GmbH
Research & Development
< Previous Next >
Follow Ups