[yast-devel] Fixing yast2-slide-show for SLE11 SP3
I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Thu, 07 Feb 2013 16:06:20 +0100 Karl Eichwalder <ke@suse.de> wrote:
I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please?
Thus far, I have checked out trunk only.
It is good start to have cloned trunk. slide show doesn't have yet SP3 repository, so it depends on which you want base it. I expect SP2. So you need these three commands: git checkout -t origin/Code-11-SP2 git checkout -b Code-11-SP3 git push origin Code-11-SP3 Now you create SP3 branch and your copy have it. So then you can commits there and when you want to push it there just call git push ( if tracked upstream is not set properly git will help you ). If you plan to use code reviews, so developers could review your changes, then documentation can be found here - https://help.github.com/articles/using-pull-requests If you find any problem, just write what it prints to you. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Josef Reidinger <jreidinger@suse.cz> writes:
It is good start to have cloned trunk.
[...]
If you find any problem, just write what it prints to you.
Thanks for your help--I think now I can manage th slide show package! -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
It's me again and this time I am about to submit translation update for SLE 12 SP1... I created the SLE-12-SP1 branch (based on SLE-12-GA), and submitted my changes (new .tar.bz2 with the translations and version increased to 3.1.13). Is this enough to make it appear in the official SLE 12 SP1 build? Or are additional git or osc actions required? -- Karl Eichwalder SUSE Linux GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, 16 Sep 2015 09:34:58 +0200 Karl Eichwalder <ke@suse.de> wrote:
It's me again and this time I am about to submit translation update for SLE 12 SP1...
I created the SLE-12-SP1 branch (based on SLE-12-GA), and submitted my changes (new .tar.bz2 with the translations and version increased to 3.1.13). Is this enough to make it appear in the official SLE 12 SP1 build? Or are additional git or osc actions required?
Hi, currently we share master for opensuse TW, Leap and also SLE-12-SP1. If you want to split SP1 from opensuse it needs additional actions, which I can do. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Josef Reidinger <jreidinger@suse.cz> writes:
I created the SLE-12-SP1 branch (based on SLE-12-GA), and submitted my changes (new .tar.bz2 with the translations and version increased to 3.1.13). Is this enough to make it appear in the official SLE 12 SP1 build? Or are additional git or osc actions required?
Hi, currently we share master for opensuse TW, Leap and also SLE-12-SP1. If you want to split SP1 from opensuse it needs additional actions, which I can do.
No, there is no need for a split. Will it appear automatically in master? -- Karl Eichwalder SUSE Linux GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, 16 Sep 2015 09:55:00 +0200 Karl Eichwalder <ke@suse.de> wrote:
Josef Reidinger <jreidinger@suse.cz> writes:
I created the SLE-12-SP1 branch (based on SLE-12-GA), and submitted my changes (new .tar.bz2 with the translations and version increased to 3.1.13). Is this enough to make it appear in the official SLE 12 SP1 build? Or are additional git or osc actions required?
Hi, currently we share master for opensuse TW, Leap and also SLE-12-SP1. If you want to split SP1 from opensuse it needs additional actions, which I can do.
No, there is no need for a split. Will it appear automatically in master?
I am not sure if I get correctly question...if you submit changes to master, it will automatically appear in opensuse and SP1. If you expect if SLE-12-SP1 branch is automatic merged to master, then no. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Josef Reidinger <jreidinger@suse.cz> writes:
I am not sure if I get correctly question...if you submit changes to master, it will automatically appear in opensuse and SP1. If you expect if SLE-12-SP1 branch is automatic merged to master, then no.
Ok, makes sense. I just created a pull request. Something with the Rakefile is probably wrong. -- Karl Eichwalder SUSE Linux GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
Josef Reidinger -
Karl Eichwalder