Hmm.. You are right. I guess people usually branch with .. Osc branch Trunk:Testing <package> -> this automatically created a home:<name>:branches:Trunk:Testing:pkg In your case, I guess it was Osc branch Trunk:Testing <package> <TGT-PRJ> -> this creates a branch using the TGT_PRJ name you have specified, in this case it was home:pohly.
On opening the package in your home project it shows the branching info. Anas, can you suggest a way around for this naming issue while branching? Regards, Madhu -----Original Message----- From: ext Patrick Ohly [mailto:[email protected]] Sent: Friday, November 12, 2010 2:47 PM To: Nanjappa Madhusudhan.3 (EXT-Wipro/Helsinki) Cc: [email protected]; [email protected]; [email protected] Subject: RE: [meego-packaging] [meego-commits] 9438: Changes to Trunk:Testing/neon On Fr, 2010-11-12 at 12:33 +0000, [email protected] wrote: > The recent SR#9442 still shows neon being submitted from home:pohly > and not home:pohly:branches:Trunk:Testing(which should be the case). What does the name have to do with it? Didn't "osc branch Trunk:Testing neon home:pohly" create a branch, as requested? Do you look at the *name* of the source project in a merge request to determine whether it is a branch or not? Obviously I'm completely ignorant of osc linking, branching, cloning. Someone please educate me. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
