Of course, that was stupid of me :D
Nevertheless, I followed your advice and it does seem to almost work now,
even though the new Problem does not have anything to do with the
communication between all those scripts, that's working fine now.
Thanks for all of your help guys.
Am Mittwoch, 13. Mai
On Sat, 23 May 2015 23:02:46 +0530
Kalpa Welivitigoda wrote:
[...]
> >> Use the `git subtree` command [*].
> > [...]
> >
> > To elaborate, a pseudocode (assuming a POSIX shell) is something
> > like this:
> >
> > $ cd repoB
> > $ git tag Bdir12 $(git subtree split dir1-2)
> >
> > $ cd ../re
Hello,
I've just started a position where we are not yet using version control at
all. The team was previously just a single developer, and now there are
three of us. I've used git before on teams, but not in an environment
exactly like this, and I need some advice.
The code we are working on
On Mon, 25 May 2015 09:30:17 -0700 (PDT)
Chris Fillmore wrote:
[...]
> In order to test our changes, the code MUST be
> running on the server -- it can't be run locally on our machines. The
> server in our office is not a production environment, it's a
> development environment. Testing and produ
Hello community I have a problem with the "new" http-backend of git.
I have set up the git-http-backend to use the "smart" http version of git.
Authentification works fine, I can clone my repository over http and https
as expected.
For testing purposes, GIT_SSL_NO_VERIFY and http.receivepack are b
