You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Shlomi Fish <sh...@iglu.org.il> on 2005/08/04 13:43:48 UTC
[ANN] SVN::Pusher version 0.01
SVN::Pusher version 0.01 was released:
http://search.cpan.org/dist/SVN-Pusher/
SVN::Pusher is a Perl module and an accompanying command line program
(svn-pusher) that can propagate changesets between two (possibly remote) URLs
of Subversion repositories.
Grab it from a CPAN mirror near you.
That's it for the announcement.
-----------------
Now for some long and boring history:
SVN::Pusher has quite a long history. After asking clkao a while ago whether
one can propagate changesets from one repository to another, and he gave me
some general guidelines, I started writing it as a Perl command line program
called "svn-push". However, I encountered some problems and since the C API
was more documented, and the people on #svn were most familiar with it, I
eventually implemented it in C. It then worked, with one glaring bug of
merging several consecutive changesets into one. I then neglected working on
it.
While I wasn't watching someone published a module SVN::Push on CPAN:
http://search.cpan.org/dist/SVN-Push/
However, this module (which has a command line program called "svnpush") acted
as a Repository-Access-layer replacement for SVN::Mirror, and as such had
several other side-effects than just propagating changesets.
I decided to convert SVN::Push into a module called SVN::Pusher which will do
the same thing as the C-based svn-push only being written in Perl, allow for
more flexibility in the code and possible future extensions. I started doing
the conversion some months ago (can't remember exactly when) but encountered
some problem, and neglected it.
A few days ago, I returned to it, was able to resolve the initial problem and
encountered some new ones. By the aid of perl -d, gdb, the good people on the
IRC, and the Subversion documentation, I was able to resolve all remaining
problems. Part of the problem was that SVN::Push did many things differently.
The code was working, but its internals were still ill-adapted to the task.
Two days ago, I cleaned up the code, adapted everything to be
SVN::Pusher-centric instead of SVN::Push-centric and uploaded it to CPAN.
So now we have:
* svn-push (the old C program)
* SVN::Push or SVN-Push (the Perl module that emulated SVN::Mirror)
* svnpush (its command line client)
* SVN::Pusher or SVN-Pusher (the Perl module that implements svn-push in Perl)
* svn-pusher (its command line client)
* svk push (a sub-command of svk)
* svn push (maybe - in the distant future, when distributed repositories will
be implemented in the Subversion core. )
Now I should try conveying this text to someone on the phone, and see if we
get back the same result. We can use Subversion (or one of its "push"
clients) to check...
Regards,
Shlomi Fish
---------------------------------------------------------------------
Shlomi Fish shlomif@iglu.org.il
Homepage: http://www.shlomifish.org/
Tcl is LISP on drugs. Using strings instead of S-expressions for closures
is Evil with one of those gigantic E's you can find at the beginning of
paragraphs.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [ANN] SVN::Pusher version 0.01
Posted by Marc Sherman <ms...@projectile.ca>.
Shlomi Fish wrote:
> SVN::Pusher version 0.01 was released:
>
> http://search.cpan.org/dist/SVN-Pusher/
>
> SVN::Pusher is a Perl module and an accompanying command line program
> (svn-pusher) that can propagate changesets between two (possibly remote) URLs
> of Subversion repositories.
[snip lots of interesting history]
Can this tool be used for maintaining a local vendor branch which
mirrors a remote svn repository? Is it possible to have it collapse
multiple remote revs into a single local rev, so that only the remote
released tags are visible in the local repository?
- Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: [ANN] SVN::Pusher version 0.01
Posted by Shlomi Fish <sh...@iglu.org.il>.
On Thursday 11 August 2005 15:00, Gerald Richter wrote:
> Hi,
>
> Also you have tried to explain much, I did't really get the difference
> between SVN::Push and SVN::Pusher.
>
> Could you please explain it to me?
>
> What are the side effects you were talking about?
>
Well, from what I could tell from the code, SVN::Push adds some data to the
repositories to keep track of what it did with each of them. So you can
propagate some changesets and then propagate the next ones without having to
specify the revisions explicitly. It also has other commands besides just
"push", which do other things.
SVN::Pusher only knows how to propagate one changest from one URL to the
other.
Regards,
Shlomi Fish
> Thanks
>
> Gerald
>
> > SVN::Pusher version 0.01 was released:
> >
> > http://search.cpan.org/dist/SVN-Pusher/
> >
> > SVN::Pusher is a Perl module and an accompanying command line program
> > (svn-pusher) that can propagate changesets between two
> > (possibly remote) URLs of Subversion repositories.
> >
> > Grab it from a CPAN mirror near you.
> >
> > That's it for the announcement.
> >
> > -----------------
> >
> > Now for some long and boring history:
> >
> > SVN::Pusher has quite a long history. After asking clkao a
> > while ago whether one can propagate changesets from one
> > repository to another, and he gave me some general
> > guidelines, I started writing it as a Perl command line
> > program called "svn-push". However, I encountered some
> > problems and since the C API was more documented, and the
> > people on #svn were most familiar with it, I eventually
> > implemented it in C. It then worked, with one glaring bug of
> > merging several consecutive changesets into one. I then
> > neglected working on it.
> >
> > While I wasn't watching someone published a module SVN::Push on CPAN:
> >
> > http://search.cpan.org/dist/SVN-Push/
> >
> > However, this module (which has a command line program called
> > "svnpush") acted as a Repository-Access-layer replacement for
> > SVN::Mirror, and as such had several other side-effects than
> > just propagating changesets.
> >
> > I decided to convert SVN::Push into a module called
> > SVN::Pusher which will do the same thing as the C-based
> > svn-push only being written in Perl, allow for more
> > flexibility in the code and possible future extensions. I
> > started doing the conversion some months ago (can't remember
> > exactly when) but encountered some problem, and neglected it.
> >
> > A few days ago, I returned to it, was able to resolve the
> > initial problem and encountered some new ones. By the aid of
> > perl -d, gdb, the good people on the IRC, and the Subversion
> > documentation, I was able to resolve all remaining problems.
> > Part of the problem was that SVN::Push did many things differently.
> >
> > The code was working, but its internals were still
> > ill-adapted to the task.
> > Two days ago, I cleaned up the code, adapted everything to be
> > SVN::Pusher-centric instead of SVN::Push-centric and uploaded
> > it to CPAN.
> >
> > So now we have:
> >
> > * svn-push (the old C program)
> > * SVN::Push or SVN-Push (the Perl module that emulated SVN::Mirror)
> > * svnpush (its command line client)
> > * SVN::Pusher or SVN-Pusher (the Perl module that implements
> > svn-push in Perl)
> > * svn-pusher (its command line client)
> > * svk push (a sub-command of svk)
> > * svn push (maybe - in the distant future, when distributed
> > repositories will be implemented in the Subversion core. )
> >
> > Now I should try conveying this text to someone on the phone,
> > and see if we get back the same result. We can use Subversion
> > (or one of its "push"
> > clients) to check...
> >
> > Regards,
> >
> > Shlomi Fish
> >
> > ---------------------------------------------------------------------
> > Shlomi Fish shlomif@iglu.org.il
> > Homepage: http://www.shlomifish.org/
> >
> > Tcl is LISP on drugs. Using strings instead of S-expressions
> > for closures is Evil with one of those gigantic E's you can
> > find at the beginning of paragraphs.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
--
---------------------------------------------------------------------
Shlomi Fish shlomif@iglu.org.il
Homepage: http://www.shlomifish.org/
Tcl is LISP on drugs. Using strings instead of S-expressions for closures
is Evil with one of those gigantic E's you can find at the beginning of
paragraphs.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: [ANN] SVN::Pusher version 0.01
Posted by Shlomi Fish <sh...@iglu.org.il>.
On Thursday 11 August 2005 15:00, Gerald Richter wrote:
> Hi,
>
> Also you have tried to explain much, I did't really get the difference
> between SVN::Push and SVN::Pusher.
>
> Could you please explain it to me?
>
> What are the side effects you were talking about?
>
Well, from what I could tell from the code, SVN::Push adds some data to the
repositories to keep track of what it did with each of them. So you can
propagate some changesets and then propagate the next ones without having to
specify the revisions explicitly. It also has other commands besides just
"push", which do other things.
SVN::Pusher only knows how to propagate one changest from one URL to the
other.
Regards,
Shlomi Fish
> Thanks
>
> Gerald
>
> > SVN::Pusher version 0.01 was released:
> >
> > http://search.cpan.org/dist/SVN-Pusher/
> >
> > SVN::Pusher is a Perl module and an accompanying command line program
> > (svn-pusher) that can propagate changesets between two
> > (possibly remote) URLs of Subversion repositories.
> >
> > Grab it from a CPAN mirror near you.
> >
> > That's it for the announcement.
> >
> > -----------------
> >
> > Now for some long and boring history:
> >
> > SVN::Pusher has quite a long history. After asking clkao a
> > while ago whether one can propagate changesets from one
> > repository to another, and he gave me some general
> > guidelines, I started writing it as a Perl command line
> > program called "svn-push". However, I encountered some
> > problems and since the C API was more documented, and the
> > people on #svn were most familiar with it, I eventually
> > implemented it in C. It then worked, with one glaring bug of
> > merging several consecutive changesets into one. I then
> > neglected working on it.
> >
> > While I wasn't watching someone published a module SVN::Push on CPAN:
> >
> > http://search.cpan.org/dist/SVN-Push/
> >
> > However, this module (which has a command line program called
> > "svnpush") acted as a Repository-Access-layer replacement for
> > SVN::Mirror, and as such had several other side-effects than
> > just propagating changesets.
> >
> > I decided to convert SVN::Push into a module called
> > SVN::Pusher which will do the same thing as the C-based
> > svn-push only being written in Perl, allow for more
> > flexibility in the code and possible future extensions. I
> > started doing the conversion some months ago (can't remember
> > exactly when) but encountered some problem, and neglected it.
> >
> > A few days ago, I returned to it, was able to resolve the
> > initial problem and encountered some new ones. By the aid of
> > perl -d, gdb, the good people on the IRC, and the Subversion
> > documentation, I was able to resolve all remaining problems.
> > Part of the problem was that SVN::Push did many things differently.
> >
> > The code was working, but its internals were still
> > ill-adapted to the task.
> > Two days ago, I cleaned up the code, adapted everything to be
> > SVN::Pusher-centric instead of SVN::Push-centric and uploaded
> > it to CPAN.
> >
> > So now we have:
> >
> > * svn-push (the old C program)
> > * SVN::Push or SVN-Push (the Perl module that emulated SVN::Mirror)
> > * svnpush (its command line client)
> > * SVN::Pusher or SVN-Pusher (the Perl module that implements
> > svn-push in Perl)
> > * svn-pusher (its command line client)
> > * svk push (a sub-command of svk)
> > * svn push (maybe - in the distant future, when distributed
> > repositories will be implemented in the Subversion core. )
> >
> > Now I should try conveying this text to someone on the phone,
> > and see if we get back the same result. We can use Subversion
> > (or one of its "push"
> > clients) to check...
> >
> > Regards,
> >
> > Shlomi Fish
> >
> > ---------------------------------------------------------------------
> > Shlomi Fish shlomif@iglu.org.il
> > Homepage: http://www.shlomifish.org/
> >
> > Tcl is LISP on drugs. Using strings instead of S-expressions
> > for closures is Evil with one of those gigantic E's you can
> > find at the beginning of paragraphs.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
--
---------------------------------------------------------------------
Shlomi Fish shlomif@iglu.org.il
Homepage: http://www.shlomifish.org/
Tcl is LISP on drugs. Using strings instead of S-expressions for closures
is Evil with one of those gigantic E's you can find at the beginning of
paragraphs.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: [ANN] SVN::Pusher version 0.01
Posted by Gerald Richter <ri...@ecos.de>.
Hi,
Also you have tried to explain much, I did't really get the difference
between SVN::Push and SVN::Pusher.
Could you please explain it to me?
What are the side effects you were talking about?
Thanks
Gerald
>
> SVN::Pusher version 0.01 was released:
>
> http://search.cpan.org/dist/SVN-Pusher/
>
> SVN::Pusher is a Perl module and an accompanying command line program
> (svn-pusher) that can propagate changesets between two
> (possibly remote) URLs of Subversion repositories.
>
> Grab it from a CPAN mirror near you.
>
> That's it for the announcement.
>
> -----------------
>
> Now for some long and boring history:
>
> SVN::Pusher has quite a long history. After asking clkao a
> while ago whether one can propagate changesets from one
> repository to another, and he gave me some general
> guidelines, I started writing it as a Perl command line
> program called "svn-push". However, I encountered some
> problems and since the C API was more documented, and the
> people on #svn were most familiar with it, I eventually
> implemented it in C. It then worked, with one glaring bug of
> merging several consecutive changesets into one. I then
> neglected working on it.
>
> While I wasn't watching someone published a module SVN::Push on CPAN:
>
> http://search.cpan.org/dist/SVN-Push/
>
> However, this module (which has a command line program called
> "svnpush") acted as a Repository-Access-layer replacement for
> SVN::Mirror, and as such had several other side-effects than
> just propagating changesets.
>
> I decided to convert SVN::Push into a module called
> SVN::Pusher which will do the same thing as the C-based
> svn-push only being written in Perl, allow for more
> flexibility in the code and possible future extensions. I
> started doing the conversion some months ago (can't remember
> exactly when) but encountered some problem, and neglected it.
>
> A few days ago, I returned to it, was able to resolve the
> initial problem and encountered some new ones. By the aid of
> perl -d, gdb, the good people on the IRC, and the Subversion
> documentation, I was able to resolve all remaining problems.
> Part of the problem was that SVN::Push did many things differently.
>
> The code was working, but its internals were still
> ill-adapted to the task.
> Two days ago, I cleaned up the code, adapted everything to be
> SVN::Pusher-centric instead of SVN::Push-centric and uploaded
> it to CPAN.
>
> So now we have:
>
> * svn-push (the old C program)
> * SVN::Push or SVN-Push (the Perl module that emulated SVN::Mirror)
> * svnpush (its command line client)
> * SVN::Pusher or SVN-Pusher (the Perl module that implements
> svn-push in Perl)
> * svn-pusher (its command line client)
> * svk push (a sub-command of svk)
> * svn push (maybe - in the distant future, when distributed
> repositories will be implemented in the Subversion core. )
>
> Now I should try conveying this text to someone on the phone,
> and see if we get back the same result. We can use Subversion
> (or one of its "push"
> clients) to check...
>
> Regards,
>
> Shlomi Fish
>
> ---------------------------------------------------------------------
> Shlomi Fish shlomif@iglu.org.il
> Homepage: http://www.shlomifish.org/
>
> Tcl is LISP on drugs. Using strings instead of S-expressions
> for closures is Evil with one of those gigantic E's you can
> find at the beginning of paragraphs.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: [ANN] SVN::Pusher version 0.01
Posted by Gerald Richter <ri...@ecos.de>.
Hi,
Also you have tried to explain much, I did't really get the difference
between SVN::Push and SVN::Pusher.
Could you please explain it to me?
What are the side effects you were talking about?
Thanks
Gerald
>
> SVN::Pusher version 0.01 was released:
>
> http://search.cpan.org/dist/SVN-Pusher/
>
> SVN::Pusher is a Perl module and an accompanying command line program
> (svn-pusher) that can propagate changesets between two
> (possibly remote) URLs of Subversion repositories.
>
> Grab it from a CPAN mirror near you.
>
> That's it for the announcement.
>
> -----------------
>
> Now for some long and boring history:
>
> SVN::Pusher has quite a long history. After asking clkao a
> while ago whether one can propagate changesets from one
> repository to another, and he gave me some general
> guidelines, I started writing it as a Perl command line
> program called "svn-push". However, I encountered some
> problems and since the C API was more documented, and the
> people on #svn were most familiar with it, I eventually
> implemented it in C. It then worked, with one glaring bug of
> merging several consecutive changesets into one. I then
> neglected working on it.
>
> While I wasn't watching someone published a module SVN::Push on CPAN:
>
> http://search.cpan.org/dist/SVN-Push/
>
> However, this module (which has a command line program called
> "svnpush") acted as a Repository-Access-layer replacement for
> SVN::Mirror, and as such had several other side-effects than
> just propagating changesets.
>
> I decided to convert SVN::Push into a module called
> SVN::Pusher which will do the same thing as the C-based
> svn-push only being written in Perl, allow for more
> flexibility in the code and possible future extensions. I
> started doing the conversion some months ago (can't remember
> exactly when) but encountered some problem, and neglected it.
>
> A few days ago, I returned to it, was able to resolve the
> initial problem and encountered some new ones. By the aid of
> perl -d, gdb, the good people on the IRC, and the Subversion
> documentation, I was able to resolve all remaining problems.
> Part of the problem was that SVN::Push did many things differently.
>
> The code was working, but its internals were still
> ill-adapted to the task.
> Two days ago, I cleaned up the code, adapted everything to be
> SVN::Pusher-centric instead of SVN::Push-centric and uploaded
> it to CPAN.
>
> So now we have:
>
> * svn-push (the old C program)
> * SVN::Push or SVN-Push (the Perl module that emulated SVN::Mirror)
> * svnpush (its command line client)
> * SVN::Pusher or SVN-Pusher (the Perl module that implements
> svn-push in Perl)
> * svn-pusher (its command line client)
> * svk push (a sub-command of svk)
> * svn push (maybe - in the distant future, when distributed
> repositories will be implemented in the Subversion core. )
>
> Now I should try conveying this text to someone on the phone,
> and see if we get back the same result. We can use Subversion
> (or one of its "push"
> clients) to check...
>
> Regards,
>
> Shlomi Fish
>
> ---------------------------------------------------------------------
> Shlomi Fish shlomif@iglu.org.il
> Homepage: http://www.shlomifish.org/
>
> Tcl is LISP on drugs. Using strings instead of S-expressions
> for closures is Evil with one of those gigantic E's you can
> find at the beginning of paragraphs.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.3 feature question
Posted by Eric Gorr <ma...@ericgorr.net>.
Ben Collins-Sussman wrote:
> There's no voting process going on for "which feature goes into 1.3".
> Lots of people are working on new features on /trunk.
Would anyone happen to be working on xattr support?
--
== Eric Gorr ========= http://www.ericgorr.net ========= ICQ:9293199 ==
"Therefore the considerations of the intelligent always include both
benefit and harm." - Sun Tzu
== Insults, like violence, are the last refuge of the incompetent... ===
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: 1.3 feature question
Posted by Ben Collins-Sussman <su...@collab.net>.
On Aug 5, 2005, at 2:37 PM, Mark Parker wrote:
>
>
> Ben Collins-Sussman wrote:
>
>> * path-based authorization for svnserve (similar to what
>> mod_dav_svn has)
>>
>
>
> Any chance that path-based authorization will be implemented as
> repository-level ACLs, so that authorization won't have to be
> implemented in each separate server?
>
No, that's a ginormous libsvn_fs schema change, probably an svn 2.0
thing. Definitely something we want. Also a tremendous source of
debate about how to design/implement. (It's *very hard* to come up
with a design for ACLs on a versioned filesystem!)
All that our Summer of Code student is doing is factorizing the
mod_authz_svn code into libsvn_repos, so that both mod_auth_svn and
svnserve can share the logic. They'll use the same authz-policy files.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: 1.3 feature question
Posted by Mark Parker <ma...@msdhub.com>.
Ben Collins-Sussman wrote:
>
> * path-based authorization for svnserve (similar to what mod_dav_svn
> has)
Any chance that path-based authorization will be implemented as
repository-level ACLs, so that authorization won't have to be
implemented in each separate server?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: 1.3 feature question
Posted by Ben Collins-Sussman <su...@collab.net>.
On Aug 5, 2005, at 9:01 AM, Miha Vitorovic wrote:
> Ben Collins-Sussman <su...@collab.net> wrote on 05.08.2005 15:05:43:
>
>
>> There's no voting process going on for "which feature goes into
>> 1.3". Lots of people are working on new features on /trunk. At some
>> point, we decide that /trunk has enough new features to justify a 1.3
>> release. Then we branch /trunk to /branches/1.3.x and let the branch
>> stabilize.
>>
>>
>
> Wasn't there a discussion somewhere about what to do next - true
> renames,
> merge tracking,... ? I remember reading something about that.
>
> But I like this approach, it must be cool to develop that way.
For those not on the dev@ list:
True renames are being worked on, but only in the repository API (it
involves a schema change.) Dunno when it will be done, but even when
it is, it won't be immediately obvious to users. It will take a long
while to get the rest of Subversion to start using the new API.
I'm working on getting svnserve to log accesses and high-level client
operations, as well as improving mod_dav_svn's logging.
Someone else is working on fixing the broken "svn checkout -N"
problem. He wants a UI which allows users to declare which
subdirectories they do/don't want, and then 'svn up' will honor the
stickiness.
We have a bunch of Summer of Code students working on new features:
* path-based authorization for svnserve (similar to what
mod_dav_svn has)
* new python bindings (that don't require pool arguments!)
* optional text-bases in the working copy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: 1.3 feature question
Posted by Miha Vitorovic <mv...@nil.si>.
Ben Collins-Sussman <su...@collab.net> wrote on 05.08.2005 15:05:43:
> There's no voting process going on for "which feature goes into
> 1.3". Lots of people are working on new features on /trunk. At some
> point, we decide that /trunk has enough new features to justify a 1.3
> release. Then we branch /trunk to /branches/1.3.x and let the branch
> stabilize.
>
Wasn't there a discussion somewhere about what to do next - true renames,
merge tracking,... ? I remember reading something about that.
But I like this approach, it must be cool to develop that way.
Cheers,
---
Miha Vitorovic
Inženir v tehničnem področju
Customer Support Engineer
NIL Data Communications, Tivolska cesta 48, 1000 Ljubljana, Slovenia
Phone +386 1 4746 500 Fax +386 1 4746 501 http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: 1.3 feature question
Posted by Ben Collins-Sussman <su...@collab.net>.
On Aug 5, 2005, at 8:00 AM, Miha Vitorovic wrote:
> Since it's a slow day, I have a question... What new major feature
> did win
> the vote for Subversion 1.3 ?
>
There's no voting process going on for "which feature goes into
1.3". Lots of people are working on new features on /trunk. At some
point, we decide that /trunk has enough new features to justify a 1.3
release. Then we branch /trunk to /branches/1.3.x and let the branch
stabilize.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
1.3 feature question
Posted by Miha Vitorovic <mv...@nil.si>.
Since it's a slow day, I have a question... What new major feature did win
the vote for Subversion 1.3 ?
Cheers,
---
Miha Vitorovic
Inženir v tehničnem področju
Customer Support Engineer
NIL Data Communications, Tivolska cesta 48, 1000 Ljubljana, Slovenia
Phone +386 1 4746 500 Fax +386 1 4746 501 http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org