Since you wrote "Any other opinions?" I assume you intended to send
this to the list... (My reply follows below.)
On Thu, Nov 7, 2019 at 5:31 AM Daniel Shahaf wrote:
> Nathan Hartman wrote on Tue, Nov 05, 2019 at 10:59:32 -0500:
> > Correct me if I'm wrong but I'm guessing that for downstream's
On Thu, Nov 7, 2019 at 6:13 AM Daniel Shahaf wrote:
> 2. As Nathan said, this can make it difficult to answer "Which unmodified
> files
> are in a changelist?". (Yes, it's still possible to answer this by parsing
> the output of «svn info», but that's far from elegant, particularly since
> it's
On 07.11.2019 21:25, Daniel Shahaf wrote:
> Consider this:
>
> [[[
> % svn info INSTALL | grep Depth
> % svn info --show-item=depth INSTALL
>
> %
> ]]]
>
> Should the second command print "infinity" instead?
Files don't have depth, printing "infinity" would be wrong. The output
is empty on purp
Consider this:
[[[
% svn info INSTALL | grep Depth
% svn info --show-item=depth INSTALL
%
]]]
Should the second command print "infinity" instead?
Cheers,
Daniel
P.S. Aside: --show-item=schedule doesn't exist. Haven't checked whether
any other fields are not selectable by --show-item..
Branko Čibej wrote:
We might want to allow using multiple options, like "--show-item=revision
--show-item=kind" in addition to comma-separated values.
I don't think this is high priority.
*And* it would require a major rewrite of our argument parser, whereas
adding a comma-separated list forma
Branko Čibej wrote on Thu, 07 Nov 2019 20:01 +00:00:
> On 07.11.2019 20:25, Daniel Shahaf wrote:
> >> We might want to allow using multiple options, like "--show-item=revision
> >> --show-item=kind" in addition to comma-separated values.
> > I don't think this is high priority.
>
> *And* it would
Daniel Shahaf wrote:
[...]> I don't see how any of these visions — leaving aside whether
they're good ideas
or not — is a blocker to the patch I posted. You're saying we could add other
features, and I'm sure we could, but that's not the right question to ask. The
question to ask is whether th
On 07.11.2019 20:25, Daniel Shahaf wrote:
> Julian Foad wrote on Thu, Nov 07, 2019 at 17:53:43 +:
> We would then have «svn info --rfc822
> --show-item=depth» that prints "Depth: empty" (with the RFC822 header)
Nitpick: it's not really RFC822 because there are spaces in the
"headers" ...
[...
Julian Foad wrote on Thu, Nov 07, 2019 at 17:53:43 +:
> We have said the outputs (except XML) simply are not intended to be parsed.
We've said that? I think what we said is that the non-XML outputs _may_ be
parsed, but with care, since they may change in minor releases as functionality
gets a
Daniel Shahaf wrote:
Branko Čibej wrote on Thu, Nov 07, 2019 at 17:28:35 +0100:
Not with a new option. Instead --show-item should accept a
comma-separated list of keywords.
You mean, like this?
It's tempting to say +1, commit it, and say we've made an improvement.
I have been missing the ab
Branko Čibej wrote on Thu, Nov 07, 2019 at 17:28:35 +0100:
> Not with a new option. Instead --show-item should accept a
> comma-separated list of keywords.
You mean, like this?
[[[
% subversion/svn/svn info wc/foo --show-item=kind,schedule,relative-url
dir add ^/foo
%
]]]
That's not a
On 07.11.2019 12:13, Daniel Shahaf wrote:
> P.S. Come to think of it, a tab-separated output mode for «svn info» might be
> nice; that is, instead of this:
> .
> % svn info README
> Path: README
> Name: README
> Working Copy Root Path: /home/daniel/src/svn/t1
> URL: https://svn
Branko Čibej wrote on Thu, 07 Nov 2019 11:57 +00:00:
> On 07.11.2019 11:39, danie...@apache.org wrote:
> > +++ pmc/subversion/machines/svn-qavm/notes.txt Thu Nov 7 10:39:27 2019
> > @@ -74,4 +74,12 @@ sudo update-rc.d wayita defaults
> > +% ssh svn-qavm3.apache.org
>
> I thought the name of the V
On 07.11.2019 11:39, danie...@apache.org wrote:
> Author: danielsh
> Date: Thu Nov 7 10:39:27 2019
> New Revision: 93535
>
> Log:
> machines: Spell out the procedure for starting wayita
>
> Modified:
> pmc/subversion/machines/svn-qavm/notes.txt
>
> Modified: pmc/subversion/machines/svn-qavm/no
Daniel Shahaf wrote:
Julian Foad wrote on Wed, Nov 06, 2019 at 16:07:23 +:
Perhaps one aspect of being in a mature and stable phase of a project's life
means that if we are going to change how an existing feature works, we
should not change it one little bit at a time like we did in early
de
Julian Foad wrote on Wed, Nov 06, 2019 at 16:07:23 +:
> Perhaps one aspect of being in a mature and stable phase of a project's life
> means that if we are going to change how an existing feature works, we
> should not change it one little bit at a time like we did in early
> development phases
Julian Foad wrote on Wed, Nov 06, 2019 at 10:36:10 +:
> Demo:
> [[[
> $ touch a b c d; svn add a b c d; svn ci -m ""; svn up
> ...
> $ echo hello > b
> $ echo hello > d
> $ svn cl foo c d
> A [foo] c
> A [foo] d
> $ svn status -v
> 11 julianfoad .
> 1
Nathan Hartman wrote on Tue, Nov 05, 2019 at 11:04:12 -0500:
> Ok. Infra fixed the issue and we have the retroactive commit emails.
Thanks for chasing that down.
> Now, who runs our #svn-dev IRC bot that reports commits? Is that also
> infra? Because that's still broken.
ASFBot is run by Infra.
18 matches
Mail list logo
