You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Stephen Davis <su...@soundgeek.org> on 2004/12/21 10:13:09 UTC
how to get a new project on the links page?
Hi,
I'm developing a Metrowerks CodeWarrior VCS plugin for Subversion and
I'd like to get my project on the links page
(http://subversion.tigris.org/project_links.html). How do I go about
doing that?
At the moment, the plugin is Mac-only but I hope to bring it to Windows
in the future. Version 0.1 has been released and I'm busy working on
version 0.2. Guinea pigs welcome.
The URL is http://www.soundgeek.org/software/SubversionPlugin.html.
BTW, CodeWarrior (unfortunately) depends on the files being read-only
in order to be considered unmodified. I heard somewhere that
Subversion 1.2 will support read-only checkouts. Is this true and is
there a timeframe for 1.2?
thanks,
stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Erik Huelsmann <e....@gmx.net>.
> On Tue, 2004-12-21 at 04:08, Stephen Davis wrote:
> > On Dec 21, 2004, at 2:57 AM, Erik Huelsmann wrote:
> >
> > >> I'm developing a Metrowerks CodeWarrior VCS plugin for Subversion and
> > >> I'd like to get my project on the links page
> > >> (http://subversion.tigris.org/project_links.html). How do I go about
> > >> doing that?
> > >
> > > Supply a patch against http://svn.collab.net/repos/svn/trunk/www on
> > > dev@.
> >
> > Thanks, will do.
> >
> > >> At the moment, the plugin is Mac-only but I hope to bring it to
> > >> Windows
> > >> in the future. Version 0.1 has been released and I'm busy working on
> > >> version 0.2. Guinea pigs welcome.
> > >>
> > >> The URL is http://www.soundgeek.org/software/SubversionPlugin.html.
> > >>
> > >> BTW, CodeWarrior (unfortunately) depends on the files being read-only
> > >> in order to be considered unmodified. I heard somewhere that
> > >> Subversion 1.2 will support read-only checkouts. Is this true and is
> > >> there a timeframe for 1.2?
> > >
> > > Subversion 1.2 will support locking. Currently development is still
> > > going
> > > on, but a preliminary estimate for 1.2 is given on the Subversion
> > > website.
> >
> > I would've looked but the tigris.org webserver appears to be having a
> > meltdown right at the moment (500 errors, java exceptions, etc.).
>
> Perhaps this is a result of the announcement about 6 hours ago that 1.2
> is now available :-)
Maybe. Except that your version number is missing a 1. prefix which *was* in
the announcement :-)
For the record: it's 1.1.2 which has been just released.
bye,
Erik.
--
+++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl
AKTION f�r Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Gary Thomas <ga...@mlbassoc.com>.
On Tue, 2004-12-21 at 04:08, Stephen Davis wrote:
> On Dec 21, 2004, at 2:57 AM, Erik Huelsmann wrote:
>
> >> I'm developing a Metrowerks CodeWarrior VCS plugin for Subversion and
> >> I'd like to get my project on the links page
> >> (http://subversion.tigris.org/project_links.html). How do I go about
> >> doing that?
> >
> > Supply a patch against http://svn.collab.net/repos/svn/trunk/www on
> > dev@.
>
> Thanks, will do.
>
> >> At the moment, the plugin is Mac-only but I hope to bring it to
> >> Windows
> >> in the future. Version 0.1 has been released and I'm busy working on
> >> version 0.2. Guinea pigs welcome.
> >>
> >> The URL is http://www.soundgeek.org/software/SubversionPlugin.html.
> >>
> >> BTW, CodeWarrior (unfortunately) depends on the files being read-only
> >> in order to be considered unmodified. I heard somewhere that
> >> Subversion 1.2 will support read-only checkouts. Is this true and is
> >> there a timeframe for 1.2?
> >
> > Subversion 1.2 will support locking. Currently development is still
> > going
> > on, but a preliminary estimate for 1.2 is given on the Subversion
> > website.
>
> I would've looked but the tigris.org webserver appears to be having a
> meltdown right at the moment (500 errors, java exceptions, etc.).
Perhaps this is a result of the announcement about 6 hours ago that 1.2
is now available :-)
--
Gary Thomas <ga...@mlbassoc.com>
MLB Associates
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Stephen Davis <su...@soundgeek.org>.
On Dec 21, 2004, at 2:57 AM, Erik Huelsmann wrote:
>> I'm developing a Metrowerks CodeWarrior VCS plugin for Subversion and
>> I'd like to get my project on the links page
>> (http://subversion.tigris.org/project_links.html). How do I go about
>> doing that?
>
> Supply a patch against http://svn.collab.net/repos/svn/trunk/www on
> dev@.
Thanks, will do.
>> At the moment, the plugin is Mac-only but I hope to bring it to
>> Windows
>> in the future. Version 0.1 has been released and I'm busy working on
>> version 0.2. Guinea pigs welcome.
>>
>> The URL is http://www.soundgeek.org/software/SubversionPlugin.html.
>>
>> BTW, CodeWarrior (unfortunately) depends on the files being read-only
>> in order to be considered unmodified. I heard somewhere that
>> Subversion 1.2 will support read-only checkouts. Is this true and is
>> there a timeframe for 1.2?
>
> Subversion 1.2 will support locking. Currently development is still
> going
> on, but a preliminary estimate for 1.2 is given on the Subversion
> website.
I would've looked but the tigris.org webserver appears to be having a
meltdown right at the moment (500 errors, java exceptions, etc.).
stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Stephen Davis <su...@soundgeek.org>.
On Dec 21, 2004, at 6:30 AM, Erik Huelsmann wrote:
> Hi,
>
>>>> BTW, CodeWarrior (unfortunately) depends on the files being
>>>> read-only
>>>> in order to be considered unmodified. I heard somewhere that
>>>> Subversion 1.2 will support read-only checkouts. Is this true and
>>>> is
>>>> there a timeframe for 1.2?
>>>
>>> Subversion 1.2 will support locking. Currently development is still
>>> going on, but a preliminary estimate for 1.2 is given on the
>>> Subversion
>>> website.
>
>> He doesn't mean locking, he's looking for read-only checkouts
>> (files are
>> flagged read only by SVN when they are unchanged). This is a
>> feature which
>> I
>> would also require... will that be in 1.2?
>
> If you don't mean files needing locks and signalling that by setting
> them
> read-only, then I guess it's currently not planned.
>
> But to say it won't be in 1.2, that depends on what exactly you expect
> from
> Subversion, how easily that could be implemented and whether someone
> will be
> taking up that task before then.
>
> So, if you want something like this, could you define the expected
> behaviour
> and have a discussion about that on dev@? That's the way we work on
> these
> additions.
> I'm thinking about behaviours+reasons like:
> - In what respect does CodeWarrior (or your tool) treat read-only files
> differently than read-write files?
It won't let you edit them until you choose "edit" or "unlock".
> - When should files be set read-write, when read-only?
Only when the user/plugin says "edit" or "unlock".
> - When is it ok to overwrite a read-only file?
Always.
> - If a file is copied, does it retain it's attributes?
AFAIK.
> - Does that include read-onlyness?
I would think.
> - How do directories fall into this picture?
Directories are candidates for locking, AFAICT.
Let me read through the current locking documents and then post a real
analysis to dev. As Ben suggested, it may do everything I want but it
also looks significantly more complex than what I am looking for.
thanks,
stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Erik Huelsmann <e....@gmx.net>.
Hi,
>>> BTW, CodeWarrior (unfortunately) depends on the files being read-only
>>> in order to be considered unmodified. I heard somewhere that
>>> Subversion 1.2 will support read-only checkouts. Is this true and is
>>> there a timeframe for 1.2?
>>
>> Subversion 1.2 will support locking. Currently development is still
>> going on, but a preliminary estimate for 1.2 is given on the Subversion
>> website.
> He doesn't mean locking, he's looking for read-only checkouts
> (files are
> flagged read only by SVN when they are unchanged). This is a
> feature which
> I
> would also require... will that be in 1.2?
If you don't mean files needing locks and signalling that by setting them
read-only, then I guess it's currently not planned.
But to say it won't be in 1.2, that depends on what exactly you expect from
Subversion, how easily that could be implemented and whether someone will be
taking up that task before then.
So, if you want something like this, could you define the expected behaviour
and have a discussion about that on dev@? That's the way we work on these
additions.
I'm thinking about behaviours+reasons like:
- In what respect does CodeWarrior (or your tool) treat read-only files
differently than read-write files?
- When should files be set read-write, when read-only?
- When is it ok to overwrite a read-only file?
- If a file is copied, does it retain it's attributes?
- Does that include read-onlyness?
- How do directories fall into this picture?
bye,
Erik.
--
+++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl
AKTION f�r Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Auto setting of the lock property for 1.2, Was: how to get a new project on the links page?
Posted by Scott Palmer <sc...@digital-rapids.com>.
On Dec 24, 2004, at 11:12 AM, Benjamin Pflugmann wrote:
> ...I cannot believe that a bit of developer
> frustration is reason enough to not deploy Subversion (presumed
> everything else meets your requirements).
Sorry I didn't mean to imply that. I've already deployed Subversion
for my project and the rest of the company is coming on board in the
new year. I just figured I should speak up as soon as I noticed the
issue. Perhaps it is too late to get something in there for the
initial 1.2 release, but the sooner people get thinking about this
issue the better.
> ... I suggest you bring your proposal
> to the attention of the dev list.
Will do. Happy holidays,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Auto setting of the lock property for 1.2, Was: how to get a new project on the links page?
Posted by Benjamin Pflugmann <be...@pflugmann.de>.
On Fri 2004-12-24 at 10:52:41 -0500, Scott Palmer wrote:
> On Dec 24, 2004, at 10:14 AM, Benjamin Pflugmann wrote:
>
> >On Fri 2004-12-24 at 09:28:54 -0500, Scott Palmer wrote:
> >>On Dec 24, 2004, at 3:02 AM, Benjamin Pflugmann wrote:
> >>>>In 1.2, will we be able to configure the server to automatically set
> >>>>this property for any file that is detected as binary?
> >>>
> >>>In Subversion's design, the server may not change any properties
> >>>without an explicit commit ...
> >>>But you can easily install a pre-commit hook that is rejecting any
> >>>commit where not all binary files have that property set...
> >>
> >>Is it the client or the server that decides if a file is binary or
> >>not?
> >
> >It's the client. ...
>
> >The decision whether a file is considered binary or not is based on
> >it's svn:mime-type property...
>
> Yes but as you point out below there is also an automated process that
> sets the mime type, so in effect the decision of whether a file is
> considered binary or not is based on a heuristic OR the mime type
> specified manually or by auto-props.
Yes, the summary is correct if you look at the effect.
[...]
> >But what you are missing to your luck is being able to set a property
> >based on the value of another property. But as was said before, you
> >can now easily reject commits having binary files without the
> >need-lock property. And writing a script for the client-side that
> >looks for all binary files and sets this property shouldn't be to hard
> >to do, either.
>
> But there is no way to use the same heuristic to set the "needs lock"
> property automatically. I think there should be.
Me too, that's what I meant with "what you are missing to your
luck..." above. We only differ on how we'd solve the problem.
> Rejecting commits with a pre-commit hook keeps the repository sane,
> but frustrates the developer because, well, it always frustrates the
> developer when a commit fails :).
Remember your original question was if it is possible. It is. And I
explained how. Yes, the solution is not perfect. But if you really
need this kind of locking, I cannot believe that a bit of developer
frustration is reason enough to not deploy Subversion (presumed
everything else meets your requirements).
> For the same reason svn:mime-type is handled automatically (e.g. you
> could just use a pre-commit hook to reject the commit in the case that
> the mime type wasn't set properly for a binary file), the same ability
> is needed for svn:lock (or whatever the name was).
I am not sure I agree on the method. Unfortunately I am not able to
give a technical reason, it's just a gut feeling. Maybe I can answer
that after some sleep. Regardless, I suggest you bring your proposal
to the attention of the dev list.
> Considering how close the current implementation is to being able to do
> this, I suggest a config option be added to tell subversion to handle
> the lock property automatically for all files that it would not do an
> automatic merge for. That seems to cover the common cases for when
> locking is really more required than optional.
Bye,
Benjamin.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Auto setting of the lock property for 1.2, Was: how to get a new project on the links page?
Posted by Scott Palmer <sc...@digital-rapids.com>.
On Dec 24, 2004, at 10:14 AM, Benjamin Pflugmann wrote:
> On Fri 2004-12-24 at 09:28:54 -0500, Scott Palmer wrote:
>> On Dec 24, 2004, at 3:02 AM, Benjamin Pflugmann wrote:
>>>> In 1.2, will we be able to configure the server to automatically set
>>>> this property for any file that is detected as binary?
>>>
>>> In Subversion's design, the server may not change any properties
>>> without an explicit commit ...
>>> But you can easily install a pre-commit hook that is rejecting any
>>> commit where not all binary files have that property set...
>>
>> Is it the client or the server that decides if a file is binary or
>> not?
>
> It's the client. ...
> The decision whether a file is considered binary or not is based on
> it's svn:mime-type property...
Yes but as you point out below there is also an automated process that
sets the mime type, so in effect the decision of whether a file is
considered binary or not is based on a heuristic OR the mime type
specified manually or by auto-props.
> http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-2.4
> describes when svn:mime-type is set and how you can influence
> automatically setting it.
"Subversion runs a very basic heuristic to determine if that file
consists of human-readable or non-human-readable content. If the
latter is the decision made, Subversion will automatically set the
svn:mime-type property on that file to application/octet-stream"
>> It would be nice if the client-side auto-props could be made to set
>> this.
> You can ...
>> Instead of using a filename pattern,
> ... but only with file patterns.
...
> But what you are missing to your luck is being able to set a property
> based on the value of another property. But as was said before, you
> can now easily reject commits having binary files without the
> need-lock property. And writing a script for the client-side that
> looks for all binary files and sets this property shouldn't be to hard
> to do, either.
But there is no way to use the same heuristic to set the "needs lock"
property automatically. I think there should be. Rejecting commits
with a pre-commit hook keeps the repository sane, but frustrates the
developer because, well, it always frustrates the developer when a
commit fails :).
For the same reason svn:mime-type is handled automatically (e.g. you
could just use a pre-commit hook to reject the commit in the case that
the mime type wasn't set properly for a binary file), the same ability
is needed for svn:lock (or whatever the name was). Manually needing to
set properties on files is awkward, that is why the auto-props feature
is present in the first place. The more things that can be effectively
automated the better.
Considering how close the current implementation is to being able to do
this, I suggest a config option be added to tell subversion to handle
the lock property automatically for all files that it would not do an
automatic merge for. That seems to cover the common cases for when
locking is really more required than optional.
Regards,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Benjamin Pflugmann <be...@pflugmann.de>.
On Fri 2004-12-24 at 09:28:54 -0500, Scott Palmer wrote:
> On Dec 24, 2004, at 3:02 AM, Benjamin Pflugmann wrote:
> > >In 1.2, will we be able to configure the server to automatically set
> > >this property for any file that is detected as binary?
> >
> >In Subversion's design, the server may not change any properties
> >without an explicit commit (because working copyies which think they
> >are up to date would break).
> >
> >But you can easily install a pre-commit hook that is rejecting any
> >commit where not all binary files have that property set. Not the
> >perfect solution, but good enough.
>
> Is it the client or the server that decides if a file is binary or not?
It's the client. The client does all eol and keyword translation, and
it's also only the client that knows the concept of line-oriented diffs.
The server knows nothing about all this, and handles everything the
same.
The decision whether a file is considered binary or not is based on
it's svn:mime-type property, see
http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-2.3.2.
http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-2.4
describes when svn:mime-type is set and how you can influence
automatically setting it.
> It would be nice if the client-side auto-props could be made to set
> this.
You can ...
> Instead of using a filename pattern,
... but only with file patterns.
> if there was a way to specify binary or not in the pattern matching
> that would be cool.
As the cited book section explains, the internal heuristic looks at
the content and should usually do the Right Thing.
But what you are missing to your luck is being able to set a property
based on the value of another property. But as was said before, you
can now easily reject commits having binary files without the
need-lock property. And writing a script for the client-side that
looks for all binary files and sets this property shouldn't be to hard
to do, either.
Bye,
Benjamin.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Scott Palmer <sc...@digital-rapids.com>.
On Dec 24, 2004, at 3:02 AM, Benjamin Pflugmann wrote:
> On Wed 2004-12-22 at 15:13:24 -0800, you wrote
>> On Tue, 21 Dec 2004 08:27:18 -0600, Ben Collins-Sussman wrote:
>>> This is our way of preventing users from editing unmergeable files
>>> without locking first (and possibly discovering existing locks,
>>> thus preventing time wastes.) The theory is that users/admins
>>> would only set this new property on unmergeable files. But if you
>>> want to set it on everything, that would work too, I guess. You'd
>>> have a 100% read-only working copy.
>>
>> In 1.2, will we be able to configure the server to automatically set
>> this property for any file that is detected as binary?
>
> In Subversion's design, the server may not change any properties
> without an explicit commit (because working copyies which think they
> are up to date would break).
>
> But you can easily install a pre-commit hook that is rejecting any
> commit where not all binary files have that property set. Not the
> perfect solution, but good enough.
Is it the client or the server that decides if a file is binary or not?
It would be nice if the client-side auto-props could be made to set
this. Instead of using a filename pattern, if there was a way to
specify binary or not in the pattern matching that would be cool.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Benjamin Pflugmann <be...@pflugmann.de>.
On Wed 2004-12-22 at 15:13:24 -0800, you wrote
> On Tue, 21 Dec 2004 08:27:18 -0600, Ben Collins-Sussman wrote:
> > This is our way of preventing users from editing unmergeable files
> > without locking first (and possibly discovering existing locks,
> > thus preventing time wastes.) The theory is that users/admins
> > would only set this new property on unmergeable files. But if you
> > want to set it on everything, that would work too, I guess. You'd
> > have a 100% read-only working copy.
>
> In 1.2, will we be able to configure the server to automatically set
> this property for any file that is detected as binary?
In Subversion's design, the server may not change any properties
without an explicit commit (because working copyies which think they
are up to date would break).
But you can easily install a pre-commit hook that is rejecting any
commit where not all binary files have that property set. Not the
perfect solution, but good enough.
Bye,
Benjamin.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Chuck Esterbrook <Ch...@yahoo.com>.
On Tue, 21 Dec 2004 08:27:18 -0600, Ben Collins-Sussman wrote:
> This is our way of preventing users from editing unmergeable files
> without locking first (and possibly discovering existing locks,
> thus preventing time wastes.) The theory is that users/admins
> would only set this new property on unmergeable files. But if you
> want to set it on everything, that would work too, I guess. You'd
> have a 100% read-only working copy.
In 1.2, will we be able to configure the server to automatically set this property for any file that is detected as binary?
-Chuck
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Dec 21, 2004, at 5:40 AM, Joerg Hessdoerfer wrote:
>
> He doesn't mean locking, he's looking for read-only checkouts (files
> are
> flagged read only by SVN when they are unchanged). This is a feature
> which I
> would also require... will that be in 1.2?
>
We've not ever planned or discussed such a feature...
But, the UI for locking is very close to this. If you attach an
'svn:needs-lock' property to a file in your project, then when you
checkout a working copy, the file in the working copy *will* be
read-only. Only by running 'svn lock foo' will the file 'foo' change
from read-only to read-write. After the lock is released, the file
goes back to the default read-only state again.
This is our way of preventing users from editing unmergeable files
without locking first (and possibly discovering existing locks, thus
preventing time wastes.) The theory is that users/admins would only
set this new property on unmergeable files. But if you want to set it
on everything, that would work too, I guess. You'd have a 100%
read-only working copy.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Joerg Hessdoerfer <Jo...@sea-gmbh.com>.
Hi,
On Tuesday 21 December 2004 11:57, Erik Huelsmann wrote:
> > Hi,
> >
> > I'm developing a Metrowerks CodeWarrior VCS plugin for Subversion and
> > I'd like to get my project on the links page
> > (http://subversion.tigris.org/project_links.html). How do I go about
> > doing that?
>
> Supply a patch against http://svn.collab.net/repos/svn/trunk/www on dev@.
>
> > At the moment, the plugin is Mac-only but I hope to bring it to Windows
> > in the future. Version 0.1 has been released and I'm busy working on
> > version 0.2. Guinea pigs welcome.
> >
> > The URL is http://www.soundgeek.org/software/SubversionPlugin.html.
> >
> > BTW, CodeWarrior (unfortunately) depends on the files being read-only
> > in order to be considered unmodified. I heard somewhere that
> > Subversion 1.2 will support read-only checkouts. Is this true and is
> > there a timeframe for 1.2?
>
> Subversion 1.2 will support locking. Currently development is still going
> on, but a preliminary estimate for 1.2 is given on the Subversion website.
>
> bye,
>
>
> Erik.
He doesn't mean locking, he's looking for read-only checkouts (files are
flagged read only by SVN when they are unchanged). This is a feature which I
would also require... will that be in 1.2?
Thanks,
Joerg
--
Leading SW developer - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW: http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how to get a new project on the links page?
Posted by Erik Huelsmann <e....@gmx.net>.
> Hi,
>
> I'm developing a Metrowerks CodeWarrior VCS plugin for Subversion and
> I'd like to get my project on the links page
> (http://subversion.tigris.org/project_links.html). How do I go about
> doing that?
Supply a patch against http://svn.collab.net/repos/svn/trunk/www on dev@.
> At the moment, the plugin is Mac-only but I hope to bring it to Windows
> in the future. Version 0.1 has been released and I'm busy working on
> version 0.2. Guinea pigs welcome.
>
> The URL is http://www.soundgeek.org/software/SubversionPlugin.html.
>
> BTW, CodeWarrior (unfortunately) depends on the files being read-only
> in order to be considered unmodified. I heard somewhere that
> Subversion 1.2 will support read-only checkouts. Is this true and is
> there a timeframe for 1.2?
Subversion 1.2 will support locking. Currently development is still going
on, but a preliminary estimate for 1.2 is given on the Subversion website.
bye,
Erik.
--
+++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl
AKTION f�r Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org