Importing subversion into git: e-mails requested and force push coming up!

[Bram Neijt]

Dear all,

I created an import of SVN into git using the SVN importer provided by
github, but that misses the SVN users account information (email
addresses)

I want to do a proper import using but I need the e-mail address you
use on github to change the commits by adding the right author
information.

1) Could everybody on this list mail me their e-mail address they want
in the commits?

antbryan = antbryan <antbryan>
bneijt = bneijt <bneijt>
hampus_wessman = hampus_wessman <hampus_wessman>
nabber00 = nabber00 <nabber00>
poeml = poeml <poeml>
t-tujikawa = t-tujikawa <t-tujikawa>


2) To rewrite the history on the metalinks git repo on github I need
to force push the newly imported repo onto the current repo. I will do
my best to keep the current commits on github alive, but please save a
local copy of https://github.com/metalink-dev/metalinks for yourself
just in case.


Greetings,

Bram

[Neil M.]

You can use this email address for me.

The two commits I've done so far aren't anything significant so if they
get clobbered its no big deal.

Another thing I've been trying to figure out is their release system.
The documentation suggests that you want to tag a release to the master,
but that would tag all the projects? Should we be making separate
branches for a release or each project? I guess I'm used to subversion
where I can just tag a subdirectory (effectively copy it) as a release
at it all makes sense.

Neil

[Tatsuhiro Tsujikawa]

On Sun, Jul 5, 2015 at 2:09 AM, Neil M. <nabb...@gmail.com> wrote:

You can use this email address for me.

The two commits I've done so far aren't anything significant so if they get clobbered its no big deal.

Another thing I've been trying to figure out is their release system. The documentation suggests that you want to tag a release to the master, but that would tag all the projects?  Should we be making separate branches for a release or each project?  I guess I'm used to subversion where I can just tag a subdirectory (effectively copy it) as a release at it all makes sense.

Neil

​It seems you can tag specific project by committing changes only for that project

http://stackoverflow.com/questions/5959622/how-to-tag-a-single-file-in-git

But, I think if each project has its own freedom (e.g., release schedule, etc​), then it is much easier to split them up to each git repository, and just place a tag on branch.

If you want to some umbrella repository, I think git submodule does the job.

Best regards,

Tatsuhiro Tsujikawa

 

On 7/4/2015 8:16 AM, Bram Neijt wrote:

Dear all,

I created an import of SVN into git using the SVN importer provided by
github, but that misses the SVN users account information (email
addresses)

I want to do a proper import using but I need the e-mail address you
use on github to change the commits by adding the right author
information.

1) Could everybody on this list mail me their e-mail address they want
in the commits?

antbryan = antbryan <antbryan>
bneijt = bneijt <bneijt>
hampus_wessman = hampus_wessman <hampus_wessman>
nabber00 = nabber00 <nabber00>
poeml = poeml <poeml>
t-tujikawa = t-tujikawa <t-tujikawa>


2) To rewrite the history on the metalinks git repo on github I need
to force push the newly imported repo onto the current repo. I will do
my best to keep the current commits on github alive, but please save a
local copy of https://github.com/metalink-dev/metalinks for yourself
just in case.


Greetings,

Bram

--
You received this message because you are subscribed to the Google Groups "Metalink Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to metalink-discus...@googlegroups.com.
To post to this group, send email to metalink-...@googlegroups.com.
Visit this group at http://groups.google.com/group/metalink-discussion.
For more options, visit https://groups.google.com/d/optout.

[Bram Neijt]

Good point! I forgot about that.

If we do not split up the repositories, the releases will all het piled up into a single list.

Seems like it would be a good thing to pull the repositories apart after all.

If everybody agrees I'll split them up.

Bram

[Bram Neijt]

Hi everybody,

I've split up the projects that had releases on SF into separate github repos.

Also I have added tags to all those projects for the releases, except
for some of the earlier checker releases that did not make it to the
separate repo because of a directory structure change.

I have added some of the downloads (see issue [1] for a checklist).

If anybody would like to copy downloads from SF to github, please feel
free to do that. I'll continue that work tomorrow, but it's easy to
see if the tag already has binaries or not so there won't be any
duplication of effort :)

Greetings,

Bram

[1] https://github.com/metalink-dev/metalinks/issues/1