Am Mittwoch, 9. Oktober 2013, 10:42:15 schrieb Erich Titl: > Hi Folks > > I was offline for the better part of a year and would like to get my > hands on the current development repository without loosing old, > possibly not committed changes. I don't have disk space to host multiple > versions and was thinking that GIT permitted to switch between the > versions in a whiff. > > This is my current git status > > mega@luna:~/leaf/devel/leaf.new/bering-uclibc> git status > # On branch openswan-2-6-38 > # Changes to be committed: > # (use "git reset HEAD <file>..." to unstage) > # > # new file: repo/openswan/openswan-2.6.38.tar.gz > # > # Changes not staged for commit: > # (use "git add <file>..." to update what will be committed) > # (use "git checkout -- <file>..." to discard changes in working > directory) > # > # modified: repo/openswan/buildtool.cfg > # > # Untracked files: > # (use "git add <file>..." to include in what will be committed) > # > # repo/initrd/files.wrap > mega@luna:~/leaf/devel/leaf.new/bering-uclibc> git diff > repo/openswan/buildtool.cfg > mega@luna:~/leaf/devel/leaf.new/bering-uclibc> git branch > maint > nameif > openswan > * openswan-2-6-38 > regdb > > I guess there have been lots of changes in structure as in content. > Could anyone try to bring me up to the current status. >
HI Erich; maybe Yves or Andrew can help more, but what I'd do is to track the master branch git branch --track master origin/master kp ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
