On Fri, 2011-06-24 at 20:31 +0200, KP Kirchdoerfer wrote: > Hi; > > just created the remote branch 4.0.1 > > This branch is intended to work fixes for 4.0.1. > I've currently only > - updated webconf to fix Trac tickets #50, #51 and #52 > - fixed bug in hash shaper (crash on initialization more than 9 networks up > to > /24 width) > and removed /bin directory. > > Feel free to add some bugfixes for 4.0.1 as well :) > > Note: It has still the old layout (bering-uclibc4). > > http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x_- > _Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM#Remote_Branches > > should us help to work with a remote branch. > > Question: Do I have as "creator" of that branch to run > git branch --track 4.0.1 origin/4.0.1 > as well? > > kp
Hi kp, Thanks. I can now see that listed when I run "git branch -r" and I can create a tracking branch with "git branch --track 4.0.1 origin/4.0.1" (which then gets listed when I run "git branch"). Do you see a local branch called 4.0.1 too? If so you won't be able to create another one. I will add some changes to the new branch so you can see if yours gets updated. Out of interest, how did you create the remote branch? Feel free to add the info to the Wiki :-) Just wondering how that branch naming is going to work out when we get to releasing 4.0.1. Normally we would create a tag "4.0.1" for the release. Won't it be confusing to have a tag and a branch with the same name? If we also need a 4.0.2 where will we maintain that - also on the branch called "4.0.1"? IMHO the branch name might be less confusing without the ".1" so e.g. simply "4.0" - but then it's the same as the 4.0 tag... Maybe "4.0-branch" or "4.0-fixes" instead? dMb ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
