Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

Hello, Sorry for my late input. I'd been considering starting a funded, but non-profit fork with close upstream collaboration just for the above reasons and for reasons even beyond that. I'm delighted that others came to a similar conclusion. Start seems probable (early?) next year. I welcome

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-13 10:45, Roman Yeryomin wrote: > On 13 October 2015 at 10:50, Bruno Randolf wrote: >> On 10/12/2015 10:53 PM, Felix Fietkau wrote: git describe r-35387-g83c5a41 If you prefer, cut the last part and get "r-35387". Looks familiar? Now

Re: [OpenWrt-Devel] SVN to GIT transition

> > People report bugs all the time, and if I'm lucky enough to have a bug > report containing revision information, I want to maximize the > likelihood of that revision information being useful (even if there are > some local commits on top of that). > Any assumptions about users thinking

Re: [OpenWrt-Devel] SVN to GIT transition

On 14 October 2015 at 10:10, Felix Fietkau wrote: > On 2015-10-13 10:45, Roman Yeryomin wrote: >> On 13 October 2015 at 10:50, Bruno Randolf wrote: >>> On 10/12/2015 10:53 PM, Felix Fietkau wrote: > git describe > > r-35387-g83c5a41 > > If

Re: [OpenWrt-Devel] SVN to GIT transition

On 13 October 2015 at 10:50, Bruno Randolf wrote: > On 10/12/2015 10:53 PM, Felix Fietkau wrote: >>> git describe >>> >>> r-35387-g83c5a41 >>> >>> If you prefer, cut the last part and get "r-35387". >>> >>> Looks familiar? Now you even have real linear numbering in each branch,

Re: [OpenWrt-Devel] SVN to GIT transition

On 13 October 2015 at 00:18, Bruno Randolf wrote: > On 10/12/2015 03:22 PM, Felix Fietkau wrote: When using tags as a starting point (via git describe), somebody has to create those tags, which is cumbersome (and would mean adding lots of useless ones). >>> >>>

Re: [OpenWrt-Devel] SVN to GIT transition

On 10/12/2015 10:53 PM, Felix Fietkau wrote: >> git describe >> >> r-35387-g83c5a41 >> >> If you prefer, cut the last part and get "r-35387". >> >> Looks familiar? Now you even have real linear numbering in each branch, >> without the gaps you get when committing to different branches in SVN + >>

Re: [OpenWrt-Devel] SVN to GIT transition

On 12 October 2015 at 22:21, Jonathan Bennett wrote: > > > On Mon, Oct 12, 2015 at 2:11 PM David Lang wrote: >> >> On Mon, 12 Oct 2015, Felix Fietkau wrote: >> >> > On 2015-10-12 16:11, Roman Yeryomin wrote: >> >> On 12 October 2015 at 16:34, Felix Fietkau

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

Hello Kaloz, is there any initiative to create a non-profit organization ? Regards, Sorin B. On Tue, Oct 13, 2015 at 1:44 PM, Imre Kaloz wrote: > On Tue, 13 Oct 2015 12:33:35 +0200, Bastian Bittorf > wrote: > > > > It should be easy possible to get

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

On Tue, 13 Oct 2015 12:33:35 +0200, Bastian Bittorf wrote: It should be easy possible to get funding from all the companies which work with OpenWrt. Is this in option? Not until we have a nonprofit organization as companies can't have tax deduction in exchange..

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

On Tue, 13 Oct 2015 12:46:00 +0200, Sorin Burjan wrote: Hello Kaloz, is there any initiative to create a non-profit organization ? We're looking into this as well other options ;) Imre ___ openwrt-devel mailing list

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

On 13.10.2015 12:44, Imre Kaloz wrote: > On Tue, 13 Oct 2015 12:33:35 +0200, Bastian Bittorf > wrote: > > > >> It should be easy possible to get funding from all the companies which >> work with OpenWrt. Is this in option? > > Not until we have a nonprofit organization

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

As far as I remember, there's no initiative going on, but the issue was brought up at the summit by different speakers. There was also a quick poll: 1. Kathy Giori asked the attendees to raise their hand if they backed the idea of an OpenWRT foundation I would say half of the presents raised

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

* Nemesis [12.10.2015 12:17]: > The Django Framework moved from SVN to github in 2012but they kept their > own bug tracker (which they redesigned with some funding to make it more > usable): https://code.djangoproject.com/ > > I think they're a good example of an open source

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

Hi! On Tue, Oct 13, 2015 at 01:22:14PM +0200, Emmanuel Deloget wrote: > On Tue, Oct 13, 2015 at 1:04 PM, Nemesis wrote: > > As far as I remember, there's no initiative going on, but the issue was > > brought up at the summit by different speakers. > > > > There was also a

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

Hello, On Tue, Oct 13, 2015 at 1:04 PM, Nemesis wrote: > > As far as I remember, there's no initiative going on, but the issue was > brought up at the summit by different speakers. > > There was also a quick poll: > > 1. Kathy Giori asked the attendees to raise their hand if

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

* Daniel Golle [13.10.2015 16:53]: > If you want an industry-driven fork, go ahead. But don't force that > model upon an existing community without understanding how major parts > of that said community is operating. What I see since a long time, is that there is simply

Re: [OpenWrt-Devel] SVN to GIT transition

On Tue, 13 Oct 2015, Roman Yeryomin wrote: Would it be possible to track the revision number in an automated way even in a git repo? So store the r number, and automatically increment on commits. Not sure if that's an option, but it seems like it might address the problem. If a user is

Re: [OpenWrt-Devel] SVN to GIT transition

Hi again, 2015-10-12 23:49 GMT+02:00 Etienne Champetier : > Hi All, > > Here are some commands to make a "full" git repo, from the "trunk" repo > (the only complaint that everyone agrees on) > We keep git commit sha's for the trunk, and we add all branches/tags > >

Re: [OpenWrt-Devel] SVN to GIT transition

On 13 October 2015 at 23:08, David Lang wrote: > On Tue, 13 Oct 2015, Roman Yeryomin wrote: > >>> >>> Would it be possible to track the revision number in an automated way >>> even >>> in a git repo? So store the r number, and automatically increment on >>> commits. Not sure if

Re: [OpenWrt-Devel] SVN to GIT transition

On Wed, 14 Oct 2015, Roman Yeryomin wrote: On 13 October 2015 at 23:08, David Lang wrote: On Tue, 13 Oct 2015, Roman Yeryomin wrote: Would it be possible to track the revision number in an automated way even in a git repo? So store the r number, and automatically increment

Re: [OpenWrt-Devel] SVN to GIT transition

On 14 October 2015 at 00:20, David Lang wrote: > On Wed, 14 Oct 2015, Roman Yeryomin wrote: > >> On 13 October 2015 at 23:08, David Lang wrote: >>> >>> On Tue, 13 Oct 2015, Roman Yeryomin wrote: >>> > > Would it be possible to track the revision number in an

Re: [OpenWrt-Devel] SVN to GIT transition

On 10/13/2015 09:08 PM, David Lang wrote: > On Tue, 13 Oct 2015, Roman Yeryomin wrote: > >>> >>> Would it be possible to track the revision number in an automated way >>> even >>> in a git repo? So store the r number, and automatically increment on >>> commits. Not sure if that's an option, but

Re: [OpenWrt-Devel] SVN to GIT transition

> > One way to avoid the ambiguity of the r-number would be to use > "git describe origin/master" then even if the local master branch has > commits, you'd get the "upstream" revision number. But, I think it's > more important to know that there have been local changes. > The git-describe two

Re: [OpenWrt-Devel] SVN to GIT transition

> > Step 5 is unnecessary, patchwork sends emails on status changes. Okay, it seems it does this only for the original submitter, right? I guess it might come in handy to send it to the ML as well, or at least make that possible in the WebUI. > I usually copy the mbox link from patchwork and do

Re: [OpenWrt-Devel] SVN to GIT transition

Let's face it though: the current workflow wrt. core patches is crappy. 1. Go to patchwork, see if there is a patch 2. If you want to comment, switch to mail client, find thread, write reply. 3. If you want to commit: download patch, go to command line, see if it applies 4. Then manually go back

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 08:38, Steven Barth wrote: > Let's face it though: the current workflow wrt. core patches is crappy. > > 1. Go to patchwork, see if there is a patch > 2. If you want to comment, switch to mail client, find thread, write reply. > 3. If you want to commit: download patch, go to

Re: [OpenWrt-Devel] SVN to GIT transition

On 12/10/2015 09:07, Steven Barth wrote: > And don't get me started about having a completely different Issuetracker with > different credentials etc. indeed there i this thing called trac which i wonder if people actually use/look at. so we really have 3 issues at hand 1) switch the core

Re: [OpenWrt-Devel] SVN to GIT transition

>> Let's face it though: the current workflow wrt. core patches is crappy. >> >> 1. Go to patchwork, see if there is a patch >> 2. If you want to comment, switch to mail client, find thread, write reply. >> 3. If you want to commit: download patch, go to command line, see if it >> applies >> 4.

Re: [OpenWrt-Devel] SVN to GIT transition

On 12/10/2015 09:36, Felix Fietkau wrote: >> Sure could use pwclient and ocassionally do, however it does essentially one >> thing >> > only: save me the download step. Yes, I can also save me the click back to >> > the >> > browser to hit accept and can do that via CLI (if I remember the

Re: [OpenWrt-Devel] SVN to GIT transition

What do you think about using something like Jira for project management(which is free for open source projects)? I know it was used by cyanogenmod with decent success. One other potential advantage would be the possibility of CI testing being tied in more closely. On Mon, Oct 12, 2015 at 1:46

Re: [OpenWrt-Devel] SVN to GIT transition

On 12/10/2015 08:38, Steven Barth wrote: > Let's face it though: the current workflow wrt. core patches is crappy. > > 1. Go to patchwork, see if there is a patch > 2. If you want to comment, switch to mail client, find thread, write reply. > 3. If you want to commit: download patch, go to

Re: [OpenWrt-Devel] SVN to GIT transition

On 12 October 2015 at 10:36, Felix Fietkau wrote: > On 2015-10-12 08:38, Steven Barth wrote: >> Let's face it though: the current workflow wrt. core patches is crappy. >> >> 1. Go to patchwork, see if there is a patch >> 2. If you want to comment, switch to mail client, find

Re: [OpenWrt-Devel] SVN to GIT transition

> > that reminded me to check, and indeed, I only use > git://git.openwrt.org/openwrt.git anyway :) > ​ I do use the openwrt mirror github hosts, and I suppose is mirroring that one. I think it's already given all the points in Git vs SVN, so I will speak about self hosting and git interfaces. I

Re: [OpenWrt-Devel] SVN to GIT transition

Hi, (just a tiny datapoint...) On Montag, 12. Oktober 2015, Felix Fietkau wrote: > Which part is cumbersome for you and how exactly would switching the > main repo to git solve it? *g* that reminded me to check, and indeed, I only use git://git.openwrt.org/openwrt.git anyway :) I *guess*

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 10:14, Steven Barth wrote: >> What would your preferred workflow be? Please list the exact series of >> steps for it. > So to summarize, based on the current workflow: > 1. Be able to send mails (and change status) from within patchwork, e.g. > how you can do it in trac, just

Re: [OpenWrt-Devel] SVN to GIT transition

On 10/12/2015 09:44 AM, John Crispin wrote: > On 12/10/2015 09:07, Steven Barth wrote: >> > And don't get me started about having a completely different Issuetracker >> > with >> > different credentials etc. > indeed there i this thing called trac which i wonder if people actually > use/look at.

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 10:43, Roman Yeryomin wrote: > On 12 October 2015 at 10:36, Felix Fietkau wrote: >> On 2015-10-12 08:38, Steven Barth wrote: >>> Let's face it though: the current workflow wrt. core patches is crappy. >>> >>> 1. Go to patchwork, see if there is a patch >>> 2. If

Re: [OpenWrt-Devel] SVN to GIT transition

>>> What would your preferred workflow be? Please list the exact series of >>> steps for it. >> So to summarize, based on the current workflow: >> 1. Be able to send mails (and change status) from within patchwork, e.g. >> how you can do it in trac, just that it gets send out to the ML and

Re: [OpenWrt-Devel] SVN to GIT transition

On 12 October 2015 at 12:04, Holger Levsen wrote: > Hi, > > (just a tiny datapoint...) > > On Montag, 12. Oktober 2015, Felix Fietkau wrote: >> Which part is cumbersome for you and how exactly would switching the >> main repo to git solve it? > > *g* > > that reminded me to

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 11:44, Javier Domingo Cansino wrote: > that reminded me to check, and indeed, I only use > git://git.openwrt.org/openwrt.git > anyway :) > > ​ > I do use the openwrt mirror github hosts, and I suppose is mirroring > that one. > > I

Re: [OpenWrt-Devel] SVN to GIT transition

> > > since kernel.org was compromised. And gitlab/github > > are pretty similar. > Sure, just giving some background on where gitolite was being used and the less-known features it has. While it works fine for packages, I don't think the pull request stuff > is very usable

Re: [OpenWrt-Devel] SVN to GIT transition

Too many voices, which blame svn and almost no advocates. So let me change this situation. As an occasional patch maker, I am fairly happy with current workflow based on git+svn mix. I *think* that this is a good solution exactly in this case and for this project. May be some random project could

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 15:09, Javier Domingo Cansino wrote: > Right now, the revision number (r) is really useful to figure > out what particular openwrt version is being used, when people report > bugs. The commit hash cannot be used as a replacement, since it might be > one that isn't

Re: [OpenWrt-Devel] SVN to GIT transition

> > Right now, the revision number (r) is really useful to figure > out what particular openwrt version is being used, when people report > bugs. The commit hash cannot be used as a replacement, since it might be > one that isn't present in the official repo. > When using tags as a starting point

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 14:29, Javier Domingo Cansino wrote: > While it works fine for packages, I don't think the pull request stuff > is very usable for OpenWrt core, which has a more centralized > development model. > One reason why we haven't moved the main repo to git yet is that we

Re: [OpenWrt-Devel] SVN to GIT transition

On 10/12/2015 01:43 PM, Felix Fietkau wrote: > When using tags as a starting point (via git describe), somebody has to > create those tags, which is cumbersome (and would mean adding lots of > useless ones). What's cumbersome? And why would you have to create useless tags? I would actually take

Re: [OpenWrt-Devel] SVN to GIT transition

2015-10-12 15:04 GMT+03:00 Felix Fietkau : > While it works fine for packages, I don't think the pull request stuff > is very usable for OpenWrt core, which has a more centralized > development model. > One reason why we haven't moved the main repo to git yet is that we lose >

Re: [OpenWrt-Devel] SVN to GIT transition

On 12 October 2015 at 16:34, Felix Fietkau wrote: > On 2015-10-12 15:09, Javier Domingo Cansino wrote: >> Right now, the revision number (r) is really useful to figure >> out what particular openwrt version is being used, when people report >> bugs. The commit hash

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 16:11, Roman Yeryomin wrote: > On 12 October 2015 at 16:34, Felix Fietkau wrote: >> On 2015-10-12 15:09, Javier Domingo Cansino wrote: >>> Right now, the revision number (r) is really useful to figure >>> out what particular openwrt version is being used,

Re: [OpenWrt-Devel] SVN to GIT transition

On 10/11/2015 01:48 PM, John Crispin wrote: > although i see the point, out of tree fork have never been relevant to > any core decision makings I understand that this is not the main concern for core OpenWRT developers, but on the other hand you must be aware that there exist several of these

Re: [OpenWrt-Devel] SVN to GIT transition

> > I haven't seen a single instance of somebody doing this, and in my > opinion it would be kind of stupid anyway :) > We don't even advertise the SVN server URL to users anymore for a reason. > This was a way to demonstrate that the forking point is not actually a problem SVN solves. Not having

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 16:20, Javier Domingo Cansino wrote: > I haven't seen a single instance of somebody doing this, and in my > opinion it would be kind of stupid anyway :) > We don't even advertise the SVN server URL to users anymore for a > reason. > > > This was a way to demonstrate

Re: [OpenWrt-Devel] SVN to GIT transition

On Mon, Oct 12, 2015 at 2:11 PM David Lang wrote: > On Mon, 12 Oct 2015, Felix Fietkau wrote: > > > On 2015-10-12 16:11, Roman Yeryomin wrote: > >> On 12 October 2015 at 16:34, Felix Fietkau wrote: > >>> On 2015-10-12 15:09, Javier Domingo Cansino wrote: >

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 22:06, David Lang wrote: > On Mon, 12 Oct 2015, Jonathan Bennett wrote: > >> His point is that users don't ever do an SVN checkout. Because the r number >> is baked into the image, it's a really easy and obvious way for an end user >> to report the revision in a bug report. I can

Re: [OpenWrt-Devel] SVN to GIT transition

On Mon, 12 Oct 2015, Felix Fietkau wrote: On 2015-10-12 22:06, David Lang wrote: On Mon, 12 Oct 2015, Jonathan Bennett wrote: His point is that users don't ever do an SVN checkout. Because the r number is baked into the image, it's a really easy and obvious way for an end user to report the

Re: [OpenWrt-Devel] SVN to GIT transition

On Mon, 12 Oct 2015, Felix Fietkau wrote: On 2015-10-12 22:02, Javier Domingo Cansino wrote: Would it be possible to track the revision number in an automated way even in a git repo? So store the r number, and automatically increment on commits. Not sure if that's an option, but

Re: [OpenWrt-Devel] SVN to GIT transition

On Mon, 12 Oct 2015 14:04:09 +0200 Felix Fietkau wrote: > If we do everything in git, we either have to constantly remember to tag > revisions, Only some milestones would have to be tagged on a regular basis. This could even be done automatically with a daily tag or such. git

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 22:28, David Lang wrote: > On Mon, 12 Oct 2015, Felix Fietkau wrote: > >> On 2015-10-12 22:02, Javier Domingo Cansino wrote: >>> Would it be possible to track the revision number in an automated >>> way even in a git repo? So store the r number, and automatically >>>

Re: [OpenWrt-Devel] SVN to GIT transition

> > We currently don't have any tags for mainline trunk, since we usually > don't directly release from it. > I would like to know how you usually release. Can you map a commit to a release, if you can't, then we may use another simpler method. $parent-$commit$dirty That would give you info

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 22:19, David Lang wrote: > On Mon, 12 Oct 2015, Felix Fietkau wrote: > >> On 2015-10-12 22:06, David Lang wrote: >>> On Mon, 12 Oct 2015, Jonathan Bennett wrote: >>> His point is that users don't ever do an SVN checkout. Because the r number is baked into the image, it's a

Re: [OpenWrt-Devel] SVN to GIT transition

On Mon, 12 Oct 2015, Felix Fietkau wrote: On 2015-10-12 22:28, David Lang wrote: On Mon, 12 Oct 2015, Felix Fietkau wrote: On 2015-10-12 22:02, Javier Domingo Cansino wrote: Would it be possible to track the revision number in an automated way even in a git repo? So store the r

Re: [OpenWrt-Devel] SVN to GIT transition

> > I have yet to see an approach for this that actually works and deals > with all the common scenarios where people fork OpenWrt and make a few > local changes. > I see I have not enough information on what are the common use cases. For me, these are the following: - User clones openwrt master,

Re: [OpenWrt-Devel] SVN to GIT transition

> > Would it be possible to track the revision number in an automated way even > in a git repo? So store the r number, and automatically increment on > commits. Not sure if that's an option, but it seems like it might address > the problem. > In git you wouldn't need such thing, the way would

Re: [OpenWrt-Devel] SVN to GIT transition

On Mon, 12 Oct 2015, Jonathan Bennett wrote: His point is that users don't ever do an SVN checkout. Because the r number is baked into the image, it's a really easy and obvious way for an end user to report the revision in a bug report. I can see the advantage in this. If we are to move to

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 16:47, Javier Domingo Cansino wrote: > Many people follow current trunk, and we need to have precise version > information for that when they report a bug. We don't want to regularly > tag stuff just to keep reported version information up to date. > > > This is already

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 22:02, Javier Domingo Cansino wrote: > Would it be possible to track the revision number in an automated > way even in a git repo? So store the r number, and automatically > increment on commits. Not sure if that's an option, but it seems > like it might address the

Re: [OpenWrt-Devel] SVN to GIT transition

So the questions to be answered to provide a build version string are. - Are you planning to use git tags for something? What are you needs for it? - What information would you like to have from the build? Examples: last upstream common commit, current commit, dirtiness, officialness. Also, I

Re: [OpenWrt-Devel] SVN to GIT transition

On 2015-10-12 23:18, Bruno Randolf wrote: > On 10/12/2015 03:22 PM, Felix Fietkau wrote: When using tags as a starting point (via git describe), somebody has to create those tags, which is cumbersome (and would mean adding lots of useless ones). >>> >>> What's cumbersome? And why

Re: [OpenWrt-Devel] SVN to GIT transition

On 11/10/2015 14:09, Jan Čermák wrote: > Hello, > > thanks for pointing that out, Steven. Yes, this is basically the main reason > why > Bedrich opened this topic. If you need to maintain sustainable OpenWrt fork > (no > flame please, there are some situations - like running "heavyweight"

Re: [OpenWrt-Devel] SVN to GIT transition

Hello, thanks for pointing that out, Steven. Yes, this is basically the main reason why Bedrich opened this topic. If you need to maintain sustainable OpenWrt fork (no flame please, there are some situations - like running "heavyweight" OpenWrt fork on a device like our Turris - when it's

Re: [OpenWrt-Devel] SVN to GIT transition

Hello John, On Sun, Oct 11, 2015 at 2:48 PM, John Crispin wrote: > > On 11/10/2015 14:09, Jan Čermák wrote: > > Hello, > > > > thanks for pointing that out, Steven. Yes, this is basically the main > > reason why > > Bedrich opened this topic. If you need to maintain

Re: [OpenWrt-Devel] SVN to GIT transition

> On 11 Oct 2015, at 14:48, John Crispin wrote: > > patches will linger in mailing list until someone has time to look at > them. the version control system used is completely irrelevant Which is true enough if the switch just encompasses moving to another VCS. However,

Re: [OpenWrt-Devel] SVN to GIT transition

Just my 2-cents IF it isn't BROKENplease DON'T fix it. On Sun, Oct 11, 2015 at 1:26 PM, Nemesis wrote: > On 10/10/2015 07:45 PM, nemesis wrote: > > On Sat, 10 Oct 2015 00:41:24 +0300, Roman Yeryomin >

Re: [OpenWrt-Devel] SVN to GIT transition

Certain things are certainly broken. The body of kernel code that OpenWrt maintains (allows to bitrot) outside the upstream kernel tree is broken. Regarding downstream forks, would using Git also make it easier for people like project turris to push appropriate changes back into OpenWrt proper?

Re: [OpenWrt-Devel] SVN to GIT transition

On 11 Oct 2015, at 14:48, John Crispin wrote: patches will linger in mailing list until someone has time to look at them. the version control system used is completely irrelevant Which is true enough if the switch just encompasses moving to another VCS. However, what has not

Re: [OpenWrt-Devel] SVN to GIT transition

On 10/10/2015 07:45 PM, nemesis wrote: > On Sat, 10 Oct 2015 00:41:24 +0300, Roman Yeryomin > wrote: >> On 9 October 2015 at 21:22, Jo-Philipp Wich wrote: >>> Hi. >>> Moving to Git seemed to have lots of traction at the summit, and I'll add my

Re: [OpenWrt-Devel] SVN to GIT transition

> Just my 2-cents > > IF it isn't BROKENplease DON'T fix it. the question here is: how much time coders (maintainers, contributors, and users) would spare if the administration was shifted to a different infrastructure. i cannot grow to like git (i still prefer darcs), but github simply

Re: [OpenWrt-Devel] SVN to GIT transition

2015-10-11 14:16 GMT-07:00 Attila Lendvai : >> Just my 2-cents >> >> IF it isn't BROKENplease DON'T fix it. > > > the question here is: how much time coders (maintainers, contributors, > and users) would spare if the administration was shifted to a > different

Re: [OpenWrt-Devel] SVN to GIT transition

On Sat, 10 Oct 2015 00:41:24 +0300, Roman Yeryomin wrote: On 9 October 2015 at 21:22, Jo-Philipp Wich wrote: Hi. Moving to Git seemed to have lots of traction at the summit, and I'll add my voice that this sounds like a step in the right direction

Re: [OpenWrt-Devel] SVN to GIT transition

2015-10-10 10:45 GMT-07:00 nemesis : > On Sat, 10 Oct 2015 00:41:24 +0300, Roman Yeryomin > wrote: >> >> On 9 October 2015 at 21:22, Jo-Philipp Wich wrote: >>> >>> Hi. >>> Moving to Git seemed to have lots of traction at the

Re: [OpenWrt-Devel] SVN to GIT transition

> There is a big problem with git, which is identifying what OpenWrt > release your image is based off. With subversion, it is fairly easy, > you have a revision number that keeps incrementing. With git, asking > people to give you their git-describe output might be a little harder. > On the plus

Re: [OpenWrt-Devel] SVN to GIT transition

One important point was IIRC, migrating from one stable branch to another is awkward since the history is different, so rebasing custom changes on top is painful. All in all there was relatively overwhelming feedback of most of the people at the summit that there lifes would be very much easier

Re: [OpenWrt-Devel] SVN to GIT transition

On 9 October 2015 at 21:22, Jo-Philipp Wich wrote: > Hi. > >> Moving to Git seemed to have lots of traction at the summit, and I'll >> add my voice that this sounds like a step in the right direction for >> OpenWrt. I'm assuming that we would want to do a proper SVN to Git >>

[OpenWrt-Devel] SVN to GIT transition

I just received word back from Eric Raymond, author of reposurgeon and known for many other projects. He has limited time, but will be willing to offer some help if we want to do a full svn to git conversion of the core OpenWrt codebase. Moving to Git seemed to have lots of traction at the

Re: [OpenWrt-Devel] SVN to GIT transition

Hi. > Moving to Git seemed to have lots of traction at the summit, and I'll > add my voice that this sounds like a step in the right direction for > OpenWrt. I'm assuming that we would want to do a proper SVN to Git > conversion, and Eric's help on this would be great, I think. My > discussion

Re: [OpenWrt-Devel] SVN to GIT transition

On Oct 9, 2015 2:21 PM, "Jo-Philipp Wich" wrote: > > Hi. > > > Moving to Git seemed to have lots of traction at the summit, and I'll > > add my voice that this sounds like a step in the right direction for > > OpenWrt. I'm assuming that we would want to do a proper SVN to Git >