Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert FATE#320342 and FATE#317775 #242

Merged
merged 10 commits into from
Nov 11, 2016
Merged

Revert FATE#320342 and FATE#317775 #242

merged 10 commits into from
Nov 11, 2016

Conversation

imobachgs
Copy link
Contributor

@imobachgs imobachgs commented Nov 11, 2016

I've reverted changes for FATE#320342 and FATE#317775 as they won't be present in SLE 12 SP2 and, moreover, it introduces a bug (that to be fixed needs to update yast-autoinstallation).

A git revert -m 1 a29db9b could do the trick (you'll need to un-revert the changelog/version changes) but I've preferred to revert commit by commit to make revision easier (I'll squash all of them when merging).

@jreidinger
Copy link
Member

but then we have to somehow merge it from CASP branch not? and does not this revert break that merge and we need do double revert?

@imobachgs
Copy link
Contributor Author

@jreidinger I don't expect this change to be merged from CASP (and even I don't want it). This feature should be only in CASP and SP3 as it's related to the installation.

On the other hand, I could just create another PR that includes those changes using simply a patch and avoiding the revert command.

@jreidinger
Copy link
Member

ok, so LGTM

@imobachgs
Copy link
Contributor Author

Thanks!

@imobachgs imobachgs merged commit 64c7131 into SLE-12-SP2 Nov 11, 2016
@imobachgs imobachgs deleted the sle-12-sp2-cleanup branch November 11, 2016 12:58
ancorgs added a commit to ancorgs/yast-storage that referenced this pull request Jan 10, 2017
Revert "Revert FATE#320342 and FATE#317775 (yast#242)"
So this is a revert of the original revert (which was targeted to SP2
and not to CASP) :-)
This reverts commit 64c7131.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants