On Tue, Jan 14, 2020 at 11:34 AM Jonathan Wakely <jwakely....@gmail.com> wrote: > > On Tue, 14 Jan 2020 at 09:22, Uros Bizjak <ubiz...@gmail.com> wrote: > > > > gcc_update, when called from newly initialized and pulled tree does not > > work: > > Initialized how?
1035 mkdir gcc 1036 cd gcc 1037 git init 1038 git pull https://gcc.gnu.org/git/gcc.git > If you do a 'git clone' then it correctly checks out master and sets > it to track origin/master. I see, I'll try this now. > > > > > --cut here-- > > $ contrib/gcc_update > > Updating GIT tree > > There is no tracking information for the current branch. > > Please specify which branch you want to rebase against. > > See git-pull(1) for details. > > > > git pull <remote> <branch> > > > > If you wish to set tracking information for this branch you can do so with: > > > > git branch --set-upstream-to=origin/<branch> master > > > > Adjusting file timestamps > > git pull of full tree failed. > > --cut here-- > > > > I would also appreciate a simple step-by step instructions on how to > > set-up the local repo and basic workflow with git for "non-power" > > users, as was the case with now obsolete instructions for anonymous > > SVN r/o access [1] and r/w access [2]. Basically, push-my-first-patch > > example. > > > > [1] https://gcc.gnu.org/svn.html > > [2] https://gcc.gnu.org/svnwrite.html > > They're still a work in progress: > https://gcc.gnu.org/git.html > https://gcc.gnu.org/gitwrite.html Yes, this is the information i was looking for. Sorry for being impatient ;) Thanks, Uros.
