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 On Sun, Jul 5, 2015, 05:21 Tatsuhiro Tsujikawa <[email protected]> wrote: > On Sun, Jul 5, 2015 at 2:09 AM, Neil M. <[email protected]> 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 [email protected]. >> To post to this group, send email to [email protected] >> . >> Visit this group at http://groups.google.com/group/metalink-discussion. >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/metalink-discussion. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/metalink-discussion. For more options, visit https://groups.google.com/d/optout.
