If theres a technical question in there, ive done svn to git conversion before.
Just minus any kind of synchronization. All the attributions and everything are preserved. I can handle converting the repo in a couple hours and transfer ownership to whomever needs it.... Just offering. On Wed, Apr 17, 2019, 4:22 PM Jeremy Huntwork < [email protected]> wrote: > > > On Wed, Apr 17, 2019 at 12:51 Pierre Labastie <[email protected]> > wrote: > >> On 17/04/2019 16:57, Jeremy Huntwork wrote: >> > On Wed, Apr 17, 2019 at 12:50 AM Pierre Labastie >> > <[email protected]> wrote: >> >> >> >> Problem is I do not know how to transfer the author name to the svn >> repo: I've >> >> tried with a "git svn" repo, but it does not transfer the author name! >> After >> >> this try (r4098), your name was not even mentioned in the commit >> message, and >> >> I felt very bad about that. Fortunately, I've been able to amend the >> message >> >> with svnadmin. But still you do not appear as the author. >> > >> > Thanks, I appreciate that effort, but it really doesn't bother me. >> > >> >> Next time, I'll use a regular svn repo, and copy the full git log >> message, so >> >> that at least your name appears... >> >> >> >> Well, maybe you could acquire (or you already have) commit rights to >> the >> >> linuxfromscratch repo? I do not think I can grant you those rights, >> but why >> >> not asking Bruce? >> >> >> >> You could then commit patches, and I would mail to alfs-discuss if I >> wanted to >> >> modify something, or modify them myself (for example for trivial >> typos, or >> >> mandatory fixes in the rare cases when something is broken), and same >> in the >> >> other direction of course! >> > >> > I'll think about that. I honestly don't know how much time I am able >> > to spend on this, it really just started as a bit of poking around. >> > >> > You mentioned you use git locally - what prevents you from moving the >> > source to a public git repo, like on Github or Gitlab and >> > collaborating there? That would seem to make things easier. >> > >> >> Actually, there are a couple of things which restrain myself from doing >> so: >> - I'm not sure of the legal status of jhalfs. Normally it is GPLv2, but >> the >> license refers to a "copyright holder", and I am not sure who is the >> "copyright holder". There is nothing in the files. As long as it is >> hosted on >> svn.linuxfromscratch.org, I think it is Gerard's and/or Bruce's problem. >> If I >> host it elsewhere, I do not know... >> - Synchronizing the public git repo and the svn repo on >> svn.linuxfromscratch.org may not be very easy. It'll certainly take some >> of my >> time, which is not extensible... >> - I make a lot of mistakes on my private repo, which I wouldn't like other >> people to see (half serious :) >> >> But they are pros, of course: >> - easier collaboration: retain original authors, even if they do not do >> the >> "push" themselves; ease of branching and merging; flexible workflows (PR, >> direct push, patches) >> - access to a lot of possibilities offered by the infrastructure >> - ... >> >> So I may go for it at some point, but not now, and only when I am sure >> about >> the legal implications. >> >> Pierre > > > > We could see what Gerard has to say, but I’m pretty confident I’m the > copyright holder. I committed the version of the license file that still > appears next to the code as well as the first versions of jhalfs itself. > > If we moved it, I would think we could just point the web pages to the new > location and not worry too much about synchronization. > > Anyway, I’m not currently the maintainer so it’s totally up to you. > > JH > > -- > http://lists.linuxfromscratch.org/listinfo/alfs-discuss > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page >
-- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
