On Saturday, May 3, 2014 1:04:32 AM UTC+2, Shirish Agarwal wrote:
Hi all,
First of all thank you to all the developers, maintainers and
community at large who answers queries like this one. Please CC me as
I'm not subscribed to this google group.
I'm on debian testing. I'm using git to
On Sunday, May 4, 2014 3:53:14 AM UTC-7, Thomas Ferris Nicolaisen wrote:
On Saturday, May 3, 2014 2:09:35 AM UTC+2, joeri...@gmail.com wrote:
Are you aware that the BFG will only remove files that have been
actually removed from the latest version of the repository? If there are
other
So, problem is somewhat because of a limitation in BitBucket, but I'll ask
it here as I think someone here might have some fresh ideas on how to work
around it. I guess it is perhaps something of a SSH question.
So I keep some dotfiles in Git repos on my personal BitBucket account. The
SSH
Stefan's suggestion to install latest EB cli tools worked for me. Much
better solution than recompiling git with openssl.
Thanks!
On Thu, May 1, 2014 at 9:58 AM, Stefan Senk ste...@senktec.com wrote:
I've had a similar issue deploying to AWS ElasticBeanstalk after upgrading
to Ubuntu 14.04.
Hello and thanks for this group
I'm new to Git ( I was asked to learn it in my last job interviews, and
I've configured it this far .. )
Master on my webserver, did a clone, put both to branch ben, did commit,
and then the push fails
http://i.snag.gy/0cyzW.jpg
Any ideas ?
Thank in advance
On Sunday, May 4, 2014 10:08:48 PM UTC+2, Thomas Ferris Nicolaisen wrote:
Any wild ideas on how I could possibly get both working over SSH?
Got it: The trick is to configure SSH aliases as described here:
Hello,
you are using a non-bare repository on the remote side. Such repositories
always have a branch checked out (read: the contents of its commits are
written to actual files on the disk). On the other side, bare repositories
are just that: bare. This means that they store all commits, but not
On Sat, May 3, 2014 at 6:41 AM, Jason Curl jcur...@gmail.com wrote:
On Sat, May 3, 2014 at 1:11 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
I often do something similar. I think the easiest is to export GIT_DIR
to the repository you want to update, and then change directory where
When trying to clone a repo from GitHub, I get this error message:
The proecedure entry point curl_multi_timeout could not be located in the
dynamic link library libcurl.dll.
Does anyone have ideas on how to resolve this? I have the latest version of
git bash (1.9.2.msysgit), and the same