I sent this and the next email to another list and didn't get any response--
I've partially resolved my issue (see next post), and I'm also beginning to
understand that branches might also solve my issue (but patches see more
straightforward.
I'm resending it here as I welcome comments and
The other post, previously sent to the wrong list:
On Sunday, October 16, 2016 09:39:41 PM rhkra...@gmail.com wrote:
> I am probably using git in an unusual way.
...
> But, I'm not sure how to handle further updates after I've made local
> changes to the source code.
>
> The one approach I can
After the process finish, send the result for me.
The best new is you need do this process once only.
On Saturday, October 15, 2016 at 8:11:44 PM UTC-3, Aleksey Tsalolikhin
wrote:
>
> Hello,
>
> I'm trying to convert an SVN repository to Git with "git-svn" and it dies
> with a seg fault.
>
> #
On Tue, 18 Oct 2016 07:08:00 -0400
rhkra...@gmail.com wrote:
> I sent this and the next email to another list and didn't get any
> response-- I've partially resolved my issue (see next post), and I'm
> also beginning to understand that branches might also solve my issue
> (but patches see more
Hello!
I have a serious problem with git, After my provider had updated to a
X86_64 architecture git crashes with various memory-related errors. This is
happening remote when pushing to the repository from my local machine as
well as trying it on a shell on the server itself.
This are
On Tue, 18 Oct 2016 07:56:31 -0700 (PDT)
Raffael Reichelt wrote:
> I have a serious problem with git, After my provider had updated to a
> X86_64 architecture git crashes with various memory-related errors.
> This is happening remote when pushing to the repository