On Wed, 3 Apr 2019, Eric Johnson wrote:
> The most obvious alternative that I can think of is to use "git-svn".
> Instead of pushing changes to Subversion, push them to Git. Keep
changes in
> Git in sync with the main Subversion repository.
>
> Whenever you're read
On Tue, Apr 2, 2019 at 10:08 PM wrote:
>
> On 04/01 09:23, Eric Johnson wrote:
> > Hi mcc,
> >
> > On Mon, Apr 1, 2019 at 5:40 AM wrote:
> >
> > > Hi,
> > >
> > > (I am not subscribed and appreciate to be CC:ed by any reply to my
> > > question. Thank you! :) )
> > >
> > > The setup is some frea
On 04/01 09:23, Eric Johnson wrote:
> Hi mcc,
>
> On Mon, Apr 1, 2019 at 5:40 AM wrote:
>
> > Hi,
> >
> > (I am not subscribed and appreciate to be CC:ed by any reply to my
> > question. Thank you! :) )
> >
> > The setup is some freaking weired and I am no native speaker...
> >
> > The setup:
Hi mcc,
On Mon, Apr 1, 2019 at 5:40 AM wrote:
> Hi,
>
> (I am not subscribed and appreciate to be CC:ed by any reply to my
> question. Thank you! :) )
>
> The setup is some freaking weired and I am no native speaker...
>
> The setup: There is a remote SVN-server, I can only access via PC "A" at
Hi,
(I am not subscribed and appreciate to be CC:ed by any reply to my
question. Thank you! :) )
The setup is some freaking weired and I am no native speaker...
The setup: There is a remote SVN-server, I can only access via PC "A" at
place "A".
I am working, compiling, developing at PC "B"
