You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Erik Huelsmann <e....@gmx.net> on 2004/01/03 10:47:43 UTC
Re: [Issue 924] "svn propset svn:executable file": Cannot set svn:executable on a directory ()
Olaf,
There were some comments yesterday about your use of the issue tracker. If
you have not seen them, please read the dev@ list archives. The main point is
that the issue tracker is not to be used for discussion. That's what the
Subversion project uses the mailing lists for. The issue tracker is used to
record outcomes of discussions from IRC and the mailing lists.
So if you have any problems with Subversion, please come to the dev@ list
and explain what it is that you think is wrong and how you would expect
Subversion to work instead. Awaiting that discussion on the list, I have closed the
issue as FIXED again for now.
Hope you come to the list and discuss/explain what you want differently (and
how) from Subversion and its community.
bye,
Erik.
> http://subversion.tigris.org/issues/show_bug.cgi?id=924
> User olh changed the following:
>
> What |Old value |New value
>
================================================================================
> Status|RESOLVED |REOPENED
>
--------------------------------------------------------------------------------
> Resolution|FIXED |
>
--------------------------------------------------------------------------------
>
>
>
>
> ------- Additional comments from olh@tigris.org Sat Jan 3 02:06:00 -0800
> 2004 -------
> you cant be serious about r3428.
> I think you must take the number of arguments required by a specific
> property into account.
> It seems svn:executable is just a yes/no flag and requires no further
> arguments.
> svn:eol-style requires at least one further argument, as example.
> Do you guys really think 'svn propset svn:executable "" script' is a good
> user interface?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: issues-help@subversion.tigris.org
>
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 924] "svn propset svn:executable file": Cannot set svn:executable on a directory ()
Posted by Erik Huelsmann <e....@gmx.net>.
Hmm. to follow up on myself:
> There is no bug in the source code. *All* properties behave like this
> after
> the issue was fixed.
Meaning that if you want it changed: there will need to be a discussion on
the setting values for properties in general.
bye,
Erik.
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 924] "svn propset svn:executable file": Cannot set svn:executable on a directory ()
Posted by Olaf Hering <ol...@suse.de>.
On Wed, Jan 07, Erik Huelsmann wrote:
> There is no dummy argument. The "" is the content of the property to set. I
> use "executable" myself, but you can store anything in it that you think
> appropriate.
I see, but it looks a bit silly to me.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 924] "svn propset svn:executable file": Cannot set svn:executable on a directory ()
Posted by Erik Huelsmann <e....@gmx.net>.
> > > ------- Additional comments from olh@tigris.org Sat Jan 3 02:06:00
> -0800
> > > 2004 -------
> > > you cant be serious about r3428.
> > > I think you must take the number of arguments required by a specific
> > > property into account.
> > > It seems svn:executable is just a yes/no flag and requires no further
> > > arguments.
> > > svn:eol-style requires at least one further argument, as example.
> > > Do you guys really think 'svn propset svn:executable "" script' is a
> good
> > > user interface?
>
> It is a good habbit to add the person who reopens a bug to the CC list.
Sorry about that.
> And closing the bug again in bugzilla will not make the bug in the
> source go away. Maybe I miss something in the sources or/and or
> documentation. But why is a dummy argument to svn:executable required,
> or supposed to be a good user interface?
There is no dummy argument. The "" is the content of the property to set. I
use "executable" myself, but you can store anything in it that you think
appropriate.
There is no bug in the source code. *All* properties behave like this after
the issue was fixed. The layout you proposed was explicitly considered and
considered inappropriate in this comment block:
""
------- Additional comments from Greg Stein Wed Oct 9 23:00:51 -0800 2002
-------
Yah... no way would we silently set the svn:executable on script. We'd
issue the warning instead. That is the same pattern that we use with
'svn commit' when you mess up the message stuff. In that case, we warn
"your probably didn't mean that. use --force to override this warning".
""
I'll probably have ticked you off by now. I'm sorry for that; I really don't
intend to, but you came in screaming "this is not good! I think that is a
bug since there is no cmdline option!" and opening issues you think are related
to the problem adding comments like "do you really think this is good?!".
This is neither constructive nor helpful. That is why I asked you to explain a
bit of your use-case (for issue 1445) and come to the list to start up a
discussion on Subversion user experience (related to issue 924).
Again, not trying to tick you off, but explaining where I come from.
bye,
Erik.
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 924] "svn propset svn:executable file": Cannot set svn:executable on a directory ()
Posted by Olaf Hering <ol...@suse.de>.
On Sat, Jan 03, Erik Huelsmann wrote:
> > http://subversion.tigris.org/issues/show_bug.cgi?id=924
>
> > User olh changed the following:
> >
> > What |Old value |New value
> >
> ================================================================================
> > Status|RESOLVED |REOPENED
> >
> --------------------------------------------------------------------------------
> > Resolution|FIXED |
> >
> --------------------------------------------------------------------------------
> >
> >
> >
> >
> > ------- Additional comments from olh@tigris.org Sat Jan 3 02:06:00 -0800
> > 2004 -------
> > you cant be serious about r3428.
> > I think you must take the number of arguments required by a specific
> > property into account.
> > It seems svn:executable is just a yes/no flag and requires no further
> > arguments.
> > svn:eol-style requires at least one further argument, as example.
> > Do you guys really think 'svn propset svn:executable "" script' is a good
> > user interface?
It is a good habbit to add the person who reopens a bug to the CC list.
And closing the bug again in bugzilla will not make the bug in the
source go away. Maybe I miss something in the sources or/and or
documentation. But why is a dummy argument to svn:executable required,
or supposed to be a good user interface?
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org