" to java/client/test/
example_build.xml to remove the space, hope nobody minds.
--steve
On Nov 9, 2006, at 11:39 AM, Steve Vinoski wrote:
>
> On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
>
>>
>> I noticed that a lot of files in qpid don't have any svn
>>
+1 to adding it.
On 12/11/06, Robert Greig <[EMAIL PROTECTED]> wrote:
On 10/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
> Can we all then please set our svn clients to use the auto-props.
We have had this problem with each svn repository the codebase has
lived in and the problem with a s
On 13/11/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
do you want to write a mail to infra and cc us. Alternately if you
irc.freenode.net and go to #asfinfra there is usually someone
that can help on-line.
Yes, I'll follow up with the infrastructure people via email.
RG
Robert,
do you want to write a mail to infra and cc us. Alternately if you
irc.freenode.net and go to #asfinfra there is usually someone
that can help on-line.
Carl.
Robert Greig wrote:
On 13/11/06, Daniel Kulp <[EMAIL PROTECTED]> wrote:
On Monday November 13 2006 10:46 am, Alan Conway wro
On 13/11/06, Daniel Kulp <[EMAIL PROTECTED]> wrote:
On Monday November 13 2006 10:46 am, Alan Conway wrote:
> Is it possible to get triggers to actually fix the properties rather
> than just abort the commit and tell you to fix them?
I don't think so. I don't think you can modify the transacti
On Nov 13, 2006, at 10:46 AM, Alan Conway wrote:
Is it possible to get triggers to actually fix the properties rather
than just abort the commit and tell you to fix them?
Doesn't look that way -- the SVN book says the following.
"Warning
Do not attempt to modify the transaction using hook sc
On Monday November 13 2006 10:46 am, Alan Conway wrote:
> Is it possible to get triggers to actually fix the properties rather
> than just abort the commit and tell you to fix them?
I don't think so. I don't think you can modify the transaction.
In anycase, I'd still prefer the "abort and have
Is it possible to get triggers to actually fix the properties rather
than just abort the commit and tell you to fix them?
On Mon, 2006-11-13 at 10:25 -0500, Daniel Kulp wrote:
> On Monday November 13 2006 10:14 am, Robert Greig wrote:
> > On 13/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
> > >
On Monday November 13 2006 10:14 am, Robert Greig wrote:
> On 13/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
> > I don't object at all to adding it, but seeing as how we're part of a
> > much larger repository, could we even make such a change without
> > getting buy-in across all the other pro
On 13/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
I don't object at all to adding it, but seeing as how we're part of a
much larger repository, could we even make such a change without
getting buy-in across all the other projects sharing this repository?
Yes that could be a problem. What w
I don't object at all to adding it, but seeing as how we're part of a
much larger repository, could we even make such a change without
getting buy-in across all the other projects sharing this repository?
--steve
On Nov 13, 2006, at 9:56 AM, Carl Trieloff wrote:
+1 to adding it.
Carl.
R
+1 to adding it.
Carl.
Robert Greig wrote:
On 10/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
Can we all then please set our svn clients to use the auto-props.
We have had this problem with each svn repository the codebase has
lived in and the problem with a solution that relies upon ev
On 10/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
Can we all then please set our svn clients to use the auto-props.
We have had this problem with each svn repository the codebase has
lived in and the problem with a solution that relies upon everyone
configuring their clients is that:
1) n
's script
> in bin, and put the svn-auto-props file in etc.
>
> --steve
>
> > Carl.
> >
> > Steve Vinoski wrote:
> >> On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
> >>> I noticed that a lot of files in qpid don't have any svn
&
ote:
>>
>> On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
>>
>>>
>>> I noticed that a lot of files in qpid don't have any svn
>>> properties set on
>>> them so they end up with mixed cr/lf issues, wrong mime types when
>>> browsing, etc.
under trunk/qpid, put Dan's script
in bin, and put the svn-auto-props file in etc.
--steve
Carl.
Steve Vinoski wrote:
On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
I noticed that a lot of files in qpid don't have any svn
properties set on
them so they end up with mixed cr
9, 2006, at 11:39 AM, Steve Vinoski wrote:
On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
I noticed that a lot of files in qpid don't have any svn
properties set on
them so they end up with mixed cr/lf issues, wrong mime types when
browsing, etc That's probably not a good thing.
Steve Vinoski wrote:
Unless someone objects, I'll run this script today in the Java tree and
commit it. I'd rather leave the C++ tree to Alan or Gordon and the Ruby
and Python trees to Rafi, unless you guys want me to take care of those
trees too, just let me know.
Done on cpp tree.
epository for the same reason. Probably should add an Apache
header to it.
Dan
> Carl.
>
> Steve Vinoski wrote:
> > On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
> >> I noticed that a lot of files in qpid don't have any svn properties
> >> set on
> >> them
;
Not at all. A slightly different version is already checked into the
tuscany repository for the same reason. Probably should add an Apache
header to it.
Dan
> Carl.
>
> Steve Vinoski wrote:
> > On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
> >> I noticed that
noticed that a lot of files in qpid don't have any svn properties
set on
them so they end up with mixed cr/lf issues, wrong mime types when
browsing, etc That's probably not a good thing.
Dan, good catch. I was about to send a similar note, as last night I
found a bunch of so
On Nov 9, 2006, at 10:57 AM, Daniel Kulp wrote:
I noticed that a lot of files in qpid don't have any svn properties
set on
them so they end up with mixed cr/lf issues, wrong mime types when
browsing, etc That's probably not a good thing.
Dan, good catch. I was about
I noticed that a lot of files in qpid don't have any svn properties set on
them so they end up with mixed cr/lf issues, wrong mime types when
browsing, etc That's probably not a good thing.
I've attached a little bash shell script that I use to fix up issues like
that in
23 matches
Mail list logo
