Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-ocl.dev] GIT layout

Hi

That makes sense and works for a simple bug fix.

I often find that one bug fix leads to another and so a simple bug/nnn doesn't work. Any solution.

    Ed

On 06/06/2011 21:20, Axel Uhl wrote:
Ed, Adolfo,

either one of you or even both can/should now +1 https://bugs.eclipse.org/bugs/show_bug.cgi?id=348470

as explained in http://wiki.eclipse.org/Git/Migrating_to_Git#Open_a_Bug

As suggested in http://wiki.eclipse.org/Git_for_Committers#Creating_a_topic_branch I would find it useful if after successful setup of our new git repository we'd stick to a convention of opening branches for bugs named bug/nnn with nnn being the bug number. Given how easy it is with git to branch and merge, I really suggest we stick to this convention for each bug fix, if possible. I think it will make our work much more transparent.

Thanks,
-- Axel



Back to the top