Re: [PATCH] fix #69251 - [6 Regression] ICE in unify_array_domain on a flexible array member

[Martin Sebor <msebor at gmail dot com>]

On 02/04/2016 09:38 AM, Jason Merrill wrote:
> On 02/04/2016 10:32 AM, Martin Sebor wrote:
> > FWIW, I keep having trouble with the repository.  Git doesn't
> > work to check things in at all
>
> The instructions here aren't working for you?
>
> https://gcc.gnu.org/wiki/GitMirror#Commit_upstream_.28git-svn.29

It doesn't (or didn't the last time I tried).  I don't recall
the error but ever since my last attempt my local copy is in
a state where each time I pull I get asked to merge.  When I
try to run git svn rebase the command never finishes.

I use Git to check out code and to manage my local branches
(usually one per bug) but when it comes time to test on another
machine I create a patch, copy it to the other machine, apply
it, test it, tweak it, and then copy it back, apply it to the
SVN copy, retest it lightly, and then check it in.  That's
obviously too many steps where things can and do go wrong.
I just haven't found a good way to avoid them.  IIUC, with
Git, I should be able to share/clone my work branch across
all the machines I test on, and also be able to push the final
changes to the origin.  I just haven't figured out a way to do
it.


> > and I have only one svn repository
> > that does.  The other one keeps giving me the error below, so
> > every time I have to retest a patch I end up copying it from one
> > machine to another, which is obviously error prone.
> >
> > $ svn switch --relocate svn://gcc.gnu.org/svn/gcc
> > svn+ssh://msebor@gcc.gnu.org/svn/gcc
> > svn: E170013: Unable to connect to a repository at URL
> > 'svn+ssh://msebor@gcc.gnu.org/svn/gcc/trunk'
> > svn: E210002: To better debug SSH connection problems, remove the -q
> > option from 'ssh' in the [tunnels] section of your Subversion
> > configuration file.
> > svn: E210002: Network connection closed unexpectedly
>
> Seems like you have ssh setup issues.

Right.  I just figured it out. I had to generate a new pair of ssh
keys on the machine and upload the public key from the machine that
can connect by running

  ssh msebor@gcc.gnu.org append-key < new-keyfile

There's a mention of doing this in the "Tips&Tricks around your
account" section way at the bottom of the Read-write SVN access
page but it's not explicit enough for my dense brain.

Martin