What is the problem with ports PR reaction delays?
bapt at FreeBSD.org
Sat Jan 25 18:59:32 UTC 2014
On Sat, Jan 25, 2014 at 10:41:22AM -0800, Alfred Perlstein wrote:
> On 1/25/14 10:32 AM, Baptiste Daroussin wrote:
> > On Sat, Jan 25, 2014 at 10:27:21AM -0800, Alfred Perlstein wrote:
> >> On 1/25/14 10:04 AM, Baptiste Daroussin wrote:
> >>> On Sat, Jan 25, 2014 at 09:36:00AM -0800, Alfred Perlstein wrote:
> >>>> On 1/25/14, 9:28 AM, John Marino wrote:
> >>>>> On 1/25/2014 18:11, Alfred Perlstein wrote:
> >>>>>> Still missing the point. Git can sit on top of svn.
> >>>>> Other than converting SVN to Git, I don't know anything about that. It
> >>>>> would never be done in an official capacity. Git is not an official
> >>>>> tool of FreeBSD.
> >>>> I encourage you to educate yourself then and then review the suggestions
> >>>> I gave.
> >>> I encourage you to give a shot at what you are suggesting. git-svn is broken for
> >>> committers as long as it doesn't properly handle properties.
> >> Or maybe our requirement for props is broken?
> >> Is $FreeBSD$ *that* important?
> >> -Alfred
> > There is not only $Freebsd$ but also other props.
> I'm wondering because there's huge projects out there not tied down to
> svn. It seems to be a problem of our own invention.
> Having managed the FreeNAS project for a year and exclusively using git
> we found ZERO use for any svn props. We just used git and put all the
> cruft behind us.
> And we were glad for it!
svn props are used by and for svn, sure if you are not in a svn world you do not
need the props, see the autoprops set on the repo for more details,
honnestly I do not care the vcs we use, right now it is svn so what ever is
going to be use on top of it it should be svn compliant and svn needs and uses
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
More information about the freebsd-ports