git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Absolute Beginner

From
MNMarcos Nogueira <marcos@arena.com.br>
Date
Nov 23, 2010, 14:16 UTC
Message-ID
<201011231216.33207.marcos@arena.com.br>
In-Reply-To
<AANLkTindQRaUMXiQ_2Fa-guKtZz5oV89Gw7W0dapO9MT@mail.gmail.com>
Hello Duy,
Thanks for your reply. Since this is my first visit to this mailing-list, I don't know its etiquette rules yet. Is this the place to get help? Can I post long messages? The whole story of setting up our Git server is quite big... :-)
Anyway, follows below a list of some of the places where I've found the instructions I've mentioned:

http://progit.org/book/ch4-0.html http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.txt http://www.howtoforge.com/how-to-install-a-public-git-repository-on-a-debian-server http://batterypowered.wordpress.com/2008/07/04/deploying-a-git-repository-server-in-ubuntu/ http://mattrude.com/2009/07/creating-a-secure-git-repository-server/ http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way http://www.kernel.org/pub/software/scm/git/docs/git-daemon.html http://gofedora.com/how-to-install-configure-gitweb/

Trying to make it short, the last attempt to push a local project to the server produced the following results:

(...) marcos@hp-laptop:~/teste_sem_bare$ git status # On branch master # Your branch is ahead of 'origin/master' by 1 commit. # nothing to commit (working directory clean)

marcos@hp-laptop:~/teste_sem_bare$ ls teste.txt

marcos@hp-laptop:~/teste_sem_bare$ git push origin master
Counting objects: 5, done.
Writing objects: 100% (3/3), 293 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error: 
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error: 
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To git@srvpkt:/home/public/teste_sem_bare
 ! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to 'git@srvpkt:/home/public/teste_sem_bare'

marcos@hp-laptop:~/teste_sem_bare$ (...)

Thanks again,
Marcos
Show 13 quoted lines
> On Tue, Nov 23, 2010 at 7:41 PM, marcos <marcos@arena.com.br> wrote:
> >
> > I'm an absolute beginner with Git. So far I've managed to install, understand
> > and use Git locally, but am facing many difficulties on using a centralized
> > repository on a LAN local server. I've followed the instructions on many
> > places over the web, but none has worked so far. As the development team
> > grows (we're 5 at this moment), consolidating and synchronizing the files is
> > becoming almost impossible. Any help will be much appreciated.
> 
> We need to know what difficulties you have. What do you want to
> achieve? What instructions have you followed? What commands have you
> tried? Any errors from them...
> 
Previous: Nguyen Thai Ngoc DuyNext: marcos
Message 3 of 8 in “Absolute Beginner”
  1. marcosNov 23, 2010
  2. Nguyen Thai Ngoc DuyNov 23, 2010
  3. Marcos NogueiraNov 23, 2010
  4. marcosNov 23, 2010
  5. Howard MillerNov 23, 2010
  6. Ilari LiusvaaraNov 23, 2010
  7. Howard MillerNov 23, 2010
  8. marcosNov 26, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.