This keeps a clean topic branch in which there are only source files
and a clean history, that can then be pushed to a public remote
repository.
-Angelo
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email
. A merge
without --squash
creates a commit merge that has as parents the topic and the
develop merge.
A push transfers all of them, including the commits on the
develop branch, that
contain the binaries.
-Angelo
--
You received this message because you are subscribed
Suppose I have a private repository and a public one. I develop using my
private repository, and at significant steps I do a commit in which I save
all, sources] and binaries. The reason for saving binaries is to allow to
recover a previously committed version without having then to rebuild all
I have the impression that the underlying model of a git repository is made
of a .git archive plus a work
directory in which (some version of, e.g. the latest) the files are
present. I.e. at least one version of
the files are stored twice.
E.g. suppose I create a new project and initialize git
running
out of ideas here :(
Thank you in advance
On Apr 20, 6:12 pm, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
On Wed, 20 Apr 2011 09:16:39 -0700 (PDT)
Angelo angelo.more...@gmail.com wrote:
[...]
Now my setup is:
(GIT remote repository server - centos) - (Dev server
Good afternoon/morning,
Few weeks ago I decided to move all our IT infrastructure from FreeBSD
to CentOS and also go away from SVN to GIT.
Installation of GIT on CentOS was as smooth as possible and went down
very well, learned the basic command line arguments and never used any
graphic tool
