https://bugzilla.novell.com/show_bug.cgi?id=352594 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |lslezak@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352594 User bluedzins@wp.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=352594#c2 --- Comment #2 from Maciej Pilichowski 2008-10-05 13:17:30 MDT --- Ladislav, I came back to this issue and check the report you linked it to. The not covered issue is "implement refresh on demand" and this report is linked to "integration with software module". a) how it is a duplicate b) since the other report is marked as fixed I believe the "refresh on demand" (on search for example) is already implemented, right? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352594 User bluedzins@wp.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=352594#c4 --- Comment #4 from Maciej Pilichowski 2008-10-06 07:04:08 MDT --- It is useful, but it described another case (very common, at least for me). And such workflow doest still not fit. Let's say I want to check if there is upgrade for kdevelop. The best move would be to start yast, search for kdevelop, refresh (this would cause getting data from repos only related to kdevelop, and nothing more) and then see if there is anything new. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.