[UrJTAG-dev] SCM sync

[Geert Stappers]

Hi,

Urjtag SVN got some commits.

How is it synchronized to git?



Groeten
Geert Stappers

[Kolja Waschk]

Hi,

Post by Geert Stappers
Urjtag SVN got some commits.
How is it synchronized to git?

I too just realized (afterwards) from old postings here that this svn >
git sync has been performed more or less manually by Mike Frysinger and
is no SourceForge service. Does the script still live somewhere?

Kolja

Post by Geert Stappers
Hi,
Groeten
Geert Stappers

[Geert Stappers]

Post by Kolja Waschk

Post by Geert Stappers
Urjtag SVN got some commits.
How is it synchronized to git?

I too just realized (afterwards) from old postings here that this svn >
git sync has been performed more or less manually by Mike Frysinger and
is no SourceForge service. Does the script still live somewhere?

Now that know there is no "auto sync", that both SCM, Source Code Management
systems, are complete seperated:

What about switching from 'subversion' to 'git'?


Groeten
Geert Stappers

P.S.
I say 'git' and I mean 'git'.

[Mike Frysinger]

Post by Geert Stappers

Post by Kolja Waschk

Post by Geert Stappers
Urjtag SVN got some commits.
How is it synchronized to git?

I too just realized (afterwards) from old postings here that this svn >
git sync has been performed more or less manually by Mike Frysinger and
is no SourceForge service. Does the script still live somewhere?

Now that know there is no "auto sync", that both SCM, Source Code Management

i synced it by hand which meant throwing out the recent merge
-mike

[Kolja Waschk]

Post by Mike Frysinger
i synced it by hand which meant throwing out the recent merge

Thanks. I was about to manually "port" the commits today or tomorrow but
hoped for a comment from you until then. How do you think about the
future of the SVN repository and SF in general though?

Kolja

[Mike Frysinger]

Post by Kolja Waschk

Post by Mike Frysinger
i synced it by hand which meant throwing out the recent merge

Thanks. I was about to manually "port" the commits today or tomorrow but
hoped for a comment from you until then. How do you think about the
future of the SVN repository and SF in general though?

imo, we should migrate to git, and to github. it wouldn't impact the
mailing list (we can keep this fine).

if we're ready to pull that trigger, we should further split the git
history into two repos -- one for the web and one for the code. i
can take care of doing that easily enough.
-mike

[CeDeROM]

github has nice ticket system :-)

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Post by Mike Frysinger

Post by Kolja Waschk

Post by Mike Frysinger
i synced it by hand which meant throwing out the recent merge

Thanks. I was about to manually "port" the commits today or tomorrow but
hoped for a comment from you until then. How do you think about the
future of the SVN repository and SF in general though?

imo, we should migrate to git, and to github. it wouldn't impact the
mailing list (we can keep this fine).
if we're ready to pull that trigger, we should further split the git
history into two repos -- one for the web and one for the code. i
can take care of doing that easily enough.
-mike
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
UrJTAG-development mailing list
https://lists.sourceforge.net/lists/listinfo/urjtag-development

[Kolja Waschk]

Hi,

Post by Mike Frysinger
imo, we should migrate to git, and to github. it wouldn't impact the
mailing list (we can keep this fine).

Ok, I didn't think about that possibility. That's another way of keeping
some part at SF for now to minimize the immediate to-do-list for a move :)

Well, if you help the project with establishing a master at github, I
(and obviously many others here) would certainly appreciate that?

In that case I'd even opt to do the very next release *there* so
everyone who integrates / packages that will already base the work on a
more future-proof source.

I'll have a look at the possibilities to transfer tickets to github, at
least some content, not necessarily the original author info.

In my ancient "release-to-do" note (found somewhere in old archives),
one of the action points is to update the NEWS file. Maybe we should do
this a last time for the upcoming release?

Kolja

[Geert Stappers]

Post by Kolja Waschk
Hi,

Post by Mike Frysinger
imo, we should migrate to git, and to github. it wouldn't impact the
mailing list (we can keep this fine).

Ok, I didn't think about that possibility. That's another way of keeping
some part at SF for now to minimize the immediate to-do-list for a move :)
Well, if you help the project with establishing a master at github, I
(and obviously many others here) would certainly appreciate that?
In that case I'd even opt to do the very next release *there* so
everyone who integrates / packages that will already base the work on a
more future-proof source.
I'll have a look at the possibilities to transfer tickets to github, at
least some content, not necessarily the original author info.

I don't know if there is a source forge counter part
of https://github.com/joeyh/github-backup

A quick search did bring me https://sourceforge.net/blog/project-data-export/
I hope it helps.


Groeten
Geert Stappers

[Kolja Waschk]

Post by Geert Stappers
A quick search did bring me

And https://github.com/cmungall/gosf2github looks promising, it can even
map usernames. I will try that.

Mike, what are the next steps towards github? I probably need some time
to become acquainted with the services there.

Kolja