regards
sitaram
--
Sitaram
This sounds very familiar to the steps requested by github. While you
create a new repo via the github web interface, github asks that you
make an initial commit with a README.
-milki
Mario,
As git doesn't know what branch you want to use, ha cannot write anything that you didn't want.
By the way, if you want, you can make gitolite do those initial commands. You can edit the git --bare command to do what you want. Obviosly not the git --bare, just make an script and call it.
Maybe sitaram knows another way
What I meant was, *without* using gitolite, just using a repo on some
user you have ssh access to.
Gitolite is just an access control layer. Gitolite does not and will
not change the behaviour of git *except* to allow/deny as rules
specify. It cannot and will not change the *content*, add dummy
commits, create branches, etc. If your NetBeans cannot deal with an
empty repo that is *not* gitolite's problem.
Sorry. Deal with it yourself; make a README file, add/commit/push
from a command line, *then* tell your IDE about the repo.
sitaram
--
Sitaram
I just thought that when gitolite creates a repo (after I push the conf with a new repo line) it should make this initial commit to create the master branch.
I'll probably have to locate where it creates and use it with this --bare option that you've told me.
Well not everyone has an IDE that can't deal with empty repos. Most
IDEs probably work fine.
Even if that were true, why should gitolite change *git*'s behaviour
in aspects that do not have anything to do with access
control/administration, i.e., in terms of *content* of the repo?
> I'll probably have to locate where it creates and use it with this --bare option that you've told me.
Or you could use a gl-post-init hook --
http://sitaramc.github.com/gitolite/doc/2-admin.html#_gl_post_init_hook
--
Sitaram