Mailinglist Archive: opensuse-buildservice (276 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] Re: [PATCH] - do_update: rewrote code path for expanding/unexpanding a wc
- From: Michael Schroeder <mls@xxxxxxx>
- Date: Thu, 29 Mar 2012 14:22:24 +0200
- Message-id: <20120329122224.GA16320@suse.de>
On Thu, Mar 29, 2012 at 01:22:27PM +0200, Marcus Hüwe wrote:
Dunno, I always thought it was:
"osc up -e": keep the current rev, but expand
"osc up -u": keep the current rev, but unexpand
I that's no longer true, we need to provide the functionality
in some way.
Cheers,
Michael.
--
Michael Schroeder mls@xxxxxxx
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx
IMHO it's a semantic question: what is "osc up -e" and "osc up -u"
supposed to do? The old behaviour was:
"osc up -e": update to the latest rev and expand it
"osc up -u": update to the current rev and don't expand it
Dunno, I always thought it was:
"osc up -e": keep the current rev, but expand
"osc up -u": keep the current rev, but unexpand
I that's no longer true, we need to provide the functionality
in some way.
Cheers,
Michael.
--
Michael Schroeder mls@xxxxxxx
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx
| < Previous | Next > |