On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:
On Apr 2 09:57 Adrian Schröter wrote (excerpt):
looking for the counterpart of "osc linkpac".
well, if you indeed still use "linkpac" you are lost here, since
no files beside the _link is in you package.
But I hope you did use "branch" command instead as recommended since
I did not do anything here.
It is unfair to now tell me what would have been recommended
to be done by others in the past.
You can not get any mercy here from me. I repeat this at any time
on many public mailing lists when someone is mentioning this antic
"linkpac" since almost exactly 6 years now.
This is our default and if you ever have released a maintenance update
you are aware of this command.
I only try now to clean up mess that OBS/osc has left
I could as well recommend you to "just have made" OBS/osc
so that no mess could ever happen.
You can als ask for a text edit which does not allow to do program bugs.
Merge conflicts is something what always can happen and all scm tools on
this planet need to deal with. And mergeing something with something removed
is not even handled at all by others.
By the way:
I wonder why "linkpac" still exist and can be used without a warning
message when users of it can get lost?
there is a usecase for it, but not for what you are doing.
And I will not suddenly add a warning there after 6 years.
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org