You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Garrett Rooney <ro...@electricjellyfish.net> on 2004/10/14 12:19:34 UTC
Externals in Spanish Translation?
What's with the new svn:externals in the spanish translation?
Is there really a need to have everyone check out two copies of the
tools directory whenever they check out the tree? Plus, the externals
are annoying in and of themselves, I hate seeing a "Performing status on
external item at..." line whenever I run 'svn status' and there's no
modifications.
Can the people responsible please rewrite the spanish translation's
build system to reference the versions of those items sitting in the
main doc directory?
Thanks,
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by kf...@collab.net.
Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com> writes:
> > Grzegorz, did you try the alternate svn:externals trick I
> > mentioned? [...] Sounds ideal to me... What do you think? :-)
>
> I'll go with manual checkouts for a while.
Okay. If it gets to be too much trouble, let us know, and we can help
work up some other solution.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com>.
On 2004-10-15, kfogel@collab.net wrote:
> Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com> writes:
> > [...]
>
> Grzegorz, did you try the alternate svn:externals trick I
> mentioned? [...] Sounds ideal to me... What do you think? :-)
I'll go with manual checkouts for a while.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
On Fri, 15 Oct 2004, Grzegorz Adam Hankiewicz wrote:
> On 2004-10-14, "Brian W. Fitzpatrick" <fi...@collab.net> wrote:
> > No it most certainly does not. This would only require that you
> > check out the doc/ directory.
>
> Yes, checking out all the other translation projects. No thanks.
>
If you didn't want to have each translation, why did you at all *think*
that all others wanted the docbook stylesheets that everyone who needs it
can download himself?
> On 2004-10-14, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> > There are considerably less people working on the translations
> > than there are people who check out the tree. There's no reason
> > to inconveninece the many in order to make it more convenient
> > for the few. I see no reason to bend over backwards to avoid
> > the need for the translators to check out the entire tree.
>
> Yes. This is why I reluctantly joined the main repository. I didn't
> want to bother others, even though apparently nobody objected first.
> Now it looks clear that none of the the project's administrators
> really considered what using the main repository would mean.
>
I think The translation in itself doesn't bother anyone, at least not me.
> I can see now that these conflicts are happening due to an incorrect
> design of the repository tree layout. First of all, I was really
> shocked to find out that the book is part of the main trunk and that
> translations hang from it too. What connection is there between a
> book tailored to end users and the C source of the tool the book
> describes? Is there any need for the book to be part of the main
> tree? Is there any need for the C developers to have a checkout
> of the book in their source tree? Does Subversion build depend on
> the doc directory or its contents in such a way as Windows depends
> on Internet Exporer? After all, the web page for the book is not
> even located at the same server as the Subversion project. So why
> do they share the repository?
>
The book is the main user documentation for the software. It is good to
include that in the release distributions. Also, when some developer adds
a new feature, it should be documented in the book. The chances of this
happening becomes even less:-) if the book is in another repository. All
other projects I've seen or worked on include their documentation in the
sources.
> 11MB of data. Which with Subversion's local duplication of data meant
> roughly 23MB of hard disk space on each developer's hard disk. That's
> certainly not needed. But why stop there? Without the tools directory
> each developer is checking out between 4 and 5MB of a Spanish version
> of the book. Why is this accepted by the developers? Do Subversion
> developers like to checkout 5MB of useless data for them?
>
You're missing the point that the stylesheets you added were readily
available and maintained somewhere else. That's not the case with the book
translations. I don't read Spanish, so I certainly won't use the
translation (or the .po file for that matter). However, I don't use
javahl either, so...
Also, you don't include the C compiler for a project written in C even if
it would be convenient for some people. If you want to make life easier
for you and the translators, Karl has already suggested how to set this up
without annoying the other developers. :-)
> Øyvind A. Holm recently bumped his 2MB directory to 6MB. I
will > likely bump it to that size too when I include translated images in
> the same way the norwegian translation does. That should be about
> 12MB of data. Useless data to most subversion developers. Why keep
> it? What is the acceptable size limit?
I don't think hard disk space is the problem. Building and testing
subversion takes much more disk space than some translations. Others on
this list have pointed out problems other than with the size itself.
Please go back and read those messages if you don't know what I'm talking
about.
>
> You are working to make Subversion a replacement of CVS. A key part
> of the free software movement, just look at the diversity of projects
> hosted by Subversion. With that goal in mind, it's simply a matter
> of time until more translations are added to the repository. Imagine
> that in about one or two years the existing translations have
> catched up in size, and four more have been added. Expecting 5MB
> of checkout data for each would mean 45MB of data. Useless data for
> most of Subversion developers.
>
Yes, this might be a problem in the future. Then we may have to
reconsider.
> Here is my request to the Subversion's administrators: please remove
> the book from the doc directory and move it to an independent
> repository. And when you do so, don't design the layout with a
> subdirectory called translations where you throw in anything you
> originally didn't care of. Move the English book into a subdirectory
> called "english", and move its currently subdirectory tools to the
> root of the repository. Example:
>
Seems like you feel that we're making a difference between English and the
other languages. But remember that the English book is the master that all
translations translate from. So the English text is special in that sense.
OTOH, if other want this reorganization, I wouldn't object.
All the above being said, I think we should try to work together as
smoothly as possible. If you plan on doing something that others might
find annoying, just ask on the list. Then wait a day or two to see if any
objections are raised. Then you may avoid such nice log messages as in
r10408 in the future. You may feel that this is a limitation on your
freedom, that talking to others is a very important part of good
collaboration.
Also, remember that all of us make mistakes. (For example, search for
lundblad in the logs and then you'll see what I mean:-) I think we have to
live with this fact, but we should try to learn something from it. It
seems like this has worked very well in this project so far, and I see no
reason at all why the Spanish translation would be an exception.
Best Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by kf...@collab.net.
Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com> writes:
> [...]
Grzegorz, did you try the alternate svn:externals trick I mentioned?
I believe it completely solves all the problems here. If my proposal
wasn't detailed enough, or if there's some reason it won't work,
please let me know.
Regarding your mail: note that I also gave reasons other than mere
size why the previous arrangement was objectionable, namely, the "two
master copies" problem. But none of that is important. The important
thing is, there's a really good solution available, by which you can
keep your translation in the main Subversion tree, and yet not have to
keep all that other stuff with it.
Sounds ideal to me... What do you think? :-)
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com>.
On 2004-10-14, "Brian W. Fitzpatrick" <fi...@collab.net> wrote:
> No it most certainly does not. This would only require that you
> check out the doc/ directory.
Yes, checking out all the other translation projects. No thanks.
On 2004-10-14, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> There are considerably less people working on the translations
> than there are people who check out the tree. There's no reason
> to inconveninece the many in order to make it more convenient
> for the few. I see no reason to bend over backwards to avoid
> the need for the translators to check out the entire tree.
Yes. This is why I reluctantly joined the main repository. I didn't
want to bother others, even though apparently nobody objected first.
Now it looks clear that none of the the project's administrators
really considered what using the main repository would mean.
I can see now that these conflicts are happening due to an incorrect
design of the repository tree layout. First of all, I was really
shocked to find out that the book is part of the main trunk and that
translations hang from it too. What connection is there between a
book tailored to end users and the C source of the tool the book
describes? Is there any need for the book to be part of the main
tree? Is there any need for the C developers to have a checkout
of the book in their source tree? Does Subversion build depend on
the doc directory or its contents in such a way as Windows depends
on Internet Exporer? After all, the web page for the book is not
even located at the same server as the Subversion project. So why
do they share the repository?
My previous replacement of the svn:externals property with a
duplicate copy of the tools was not well met, especially since it
involved additional +11MB of data. Surely that's not needed in the
Subversion development tree, and that's why it was removed and a
beautiful log message attached to the operation stating that the
directory should never ever be recovered again.
11MB of data. Which with Subversion's local duplication of data meant
roughly 23MB of hard disk space on each developer's hard disk. That's
certainly not needed. But why stop there? Without the tools directory
each developer is checking out between 4 and 5MB of a Spanish version
of the book. Why is this accepted by the developers? Do Subversion
developers like to checkout 5MB of useless data for them?
Øyvind A. Holm recently bumped his 2MB directory to 6MB. I will
likely bump it to that size too when I include translated images in
the same way the norwegian translation does. That should be about
12MB of data. Useless data to most subversion developers. Why keep
it? What is the acceptable size limit?
You are working to make Subversion a replacement of CVS. A key part
of the free software movement, just look at the diversity of projects
hosted by Subversion. With that goal in mind, it's simply a matter
of time until more translations are added to the repository. Imagine
that in about one or two years the existing translations have
catched up in size, and four more have been added. Expecting 5MB
of checkout data for each would mean 45MB of data. Useless data for
most of Subversion developers.
And even in that case, there would be considerably less people
working on the translations than there are people who check out
the tree, as Garrett lucidly points out. Why even allow them to
create such an inconvenience for the many in order to make it more
convenient for the few? How long until this monolithic approach
doesn't scale well any more?
Here is my request to the Subversion's administrators: please remove
the book from the doc directory and move it to an independent
repository. And when you do so, don't design the layout with a
subdirectory called translations where you throw in anything you
originally didn't care of. Move the English book into a subdirectory
called "english", and move its currently subdirectory tools to the
root of the repository. Example:
/french
/english
/tools
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Grzegorz Adam Hankiewicz wrote:
> On 2004-10-14, "Brian W. Fitzpatrick" <fi...@collab.net> wrote:
>
>>>2. Avoid people involved in the translation proyect or following
>>> users to need a full tree checkout to build the book.
>>
>>Whoa whoa whoa whoa there a second. You're *really* blowing this
>>out of proportion. The main point here is this:
>>
>> You are causing people who checkout the Subversion source
>>tree to get the tools directory TWICE. Change your book's build
>>file to use the tools directory in /doc/book/tools.
>
>
> Conflicts with point 2.
There are considerably less people working on the translations than
there are people who check out the tree. There's no reason to
inconveninece the many in order to make it more convenient for the few.
I see no reason to bend over backwards to avoid the need for the
translators to check out the entire tree.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by "Brian W. Fitzpatrick" <fi...@collab.net>.
On Oct 14, 2004, at 5:20 PM, Grzegorz Adam Hankiewicz wrote:
> On 2004-10-14, "Brian W. Fitzpatrick" <fi...@collab.net> wrote:
>>> 2. Avoid people involved in the translation proyect or following
>>> users to need a full tree checkout to build the book.
>>
>> Whoa whoa whoa whoa there a second. You're *really* blowing this
>> out of proportion. The main point here is this:
>>
>> You are causing people who checkout the Subversion source
>> tree to get the tools directory TWICE. Change your book's build
>> file to use the tools directory in /doc/book/tools.
>
> Conflicts with point 2.
No it most certainly does not. This would only require that you check
out the doc/ directory.
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com>.
On 2004-10-14, "Brian W. Fitzpatrick" <fi...@collab.net> wrote:
> > 2. Avoid people involved in the translation proyect or following
> > users to need a full tree checkout to build the book.
>
> Whoa whoa whoa whoa there a second. You're *really* blowing this
> out of proportion. The main point here is this:
>
> You are causing people who checkout the Subversion source
> tree to get the tools directory TWICE. Change your book's build
> file to use the tools directory in /doc/book/tools.
Conflicts with point 2.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by "Brian W. Fitzpatrick" <fi...@collab.net>.
On Thu, 2004-10-14 at 15:33, Grzegorz Adam Hankiewicz wrote:
> On 2004-10-14, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> > Can the people responsible please rewrite the spanish translation's
> > build system to reference the versions of those items sitting in
> > the main doc directory?
>
> On 2004-10-14, kfogel@collab.net wrote:
> > +1
> >
> > I could see us using svn:externals to pull something in from a
> > foreign repository, but it seems silly to use it for this.
>
> On 2004-10-14, "Brian W. Fitzpatrick" <fi...@collab.net> wrote:
> > +1
>
> The purpose of using externals is to:
>
> 1a. Avoid every user to perform two checkouts where one can be
> done if it is decided to avoid including the tools directory
> in the spanish directory to optimize disk space on the server.
>
> 1b. Avoid maintenance problems in terms of syncronization if it is
> decided to duplicate the tools directory another time in the
> spanish directory.
>
> 2. Avoid people involved in the translation proyect or following
> users to need a full tree checkout to build the book.
>
> I am astonished that a feature Subversion offers to either avoid
> maintenance issues for the coordinator or maintenance issues for
> the users, instead of being applauded is considered annoying.
>
> However, since I already gave up decision freedom by joining the
> main repository, and don't feel like going back, I have chosen 1b
> from the two lesser devils as end user satisfaction is a priority.
>
> It would be also be a good time to document somewhere the banning
> of this feature (and maybe others too?) for future reference. I
> wouldn't like to start using mime-types to later learn they are
> also an unwanted baggage for the rest of the repository's users.
Whoa whoa whoa whoa there a second. You're *really* blowing this out of
proportion. The main point here is this:
You are causing people who checkout the Subversion source tree to
get the tools directory TWICE. Change your book's build file to use the
tools directory in /doc/book/tools.
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by kf...@collab.net.
Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com> writes:
> 1a. Avoid every user to perform two checkouts where one can be
> done if it is decided to avoid including the tools directory
> in the spanish directory to optimize disk space on the server.
>
> 1b. Avoid maintenance problems in terms of syncronization if it is
> decided to duplicate the tools directory another time in the
> spanish directory.
>
> 2. Avoid people involved in the translation proyect or following
> users to need a full tree checkout to build the book.
>
> I am astonished that a feature Subversion offers to either avoid
> maintenance issues for the coordinator or maintenance issues for
> the users, instead of being applauded is considered annoying.
All of this is true, but the feature doesn't come without a cost. As
described in another mail (which you should see around the same time
as this one), there is a different way to use svn:externals to
accomplish your goals, without imposing its costs on the rest of the
project.
> It would be also be a good time to document somewhere the banning
> of this feature (and maybe others too?) for future reference. I
> wouldn't like to start using mime-types to later learn they are
> also an unwanted baggage for the rest of the repository's users.
It's not banned.
The objection was to *this way* of using it, not to the general idea
of using it. We use it very happily in the cvs2svn project, for
example, and we would use it here if there were a compelling reason
to.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by Grzegorz Adam Hankiewicz <gr...@titanium.sabren.com>.
On 2004-10-14, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> Can the people responsible please rewrite the spanish translation's
> build system to reference the versions of those items sitting in
> the main doc directory?
On 2004-10-14, kfogel@collab.net wrote:
> +1
>
> I could see us using svn:externals to pull something in from a
> foreign repository, but it seems silly to use it for this.
On 2004-10-14, "Brian W. Fitzpatrick" <fi...@collab.net> wrote:
> +1
The purpose of using externals is to:
1a. Avoid every user to perform two checkouts where one can be
done if it is decided to avoid including the tools directory
in the spanish directory to optimize disk space on the server.
1b. Avoid maintenance problems in terms of syncronization if it is
decided to duplicate the tools directory another time in the
spanish directory.
2. Avoid people involved in the translation proyect or following
users to need a full tree checkout to build the book.
I am astonished that a feature Subversion offers to either avoid
maintenance issues for the coordinator or maintenance issues for
the users, instead of being applauded is considered annoying.
However, since I already gave up decision freedom by joining the
main repository, and don't feel like going back, I have chosen 1b
from the two lesser devils as end user satisfaction is a priority.
It would be also be a good time to document somewhere the banning
of this feature (and maybe others too?) for future reference. I
wouldn't like to start using mime-types to later learn they are
also an unwanted baggage for the rest of the repository's users.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by kf...@collab.net.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> What's with the new svn:externals in the spanish translation?
>
> Is there really a need to have everyone check out two copies of the
> tools directory whenever they check out the tree? Plus, the externals
> are annoying in and of themselves, I hate seeing a "Performing status
> on external item at..." line whenever I run 'svn status' and there's
> no modifications.
>
> Can the people responsible please rewrite the spanish translation's
> build system to reference the versions of those items sitting in the
> main doc directory?
+1
I could see us using svn:externals to pull something in from a foreign
repository, but it seems silly to use it for this.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by "Brian W. Fitzpatrick" <fi...@collab.net>.
On Oct 14, 2004, at 7:19 AM, Garrett Rooney wrote:
> What's with the new svn:externals in the spanish translation?
>
> Is there really a need to have everyone check out two copies of the
> tools directory whenever they check out the tree? Plus, the externals
> are annoying in and of themselves, I hate seeing a "Performing status
> on external item at..." line whenever I run 'svn status' and there's
> no modifications.
>
> Can the people responsible please rewrite the spanish translation's
> build system to reference the versions of those items sitting in the
> main doc directory?
+1
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals broken for https: or port 81 [was: Externals in Spanish
Translation?]
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Julian Foad wrote:
> Philip Martin wrote:
>
>> Besides the cosmetic uglyness of our svn:externals, it doesn't work
>> properly for anyone using using https:// or port 81 :-(
>
>
> That sounds like something that should be in the issue tracker. Please
> could you raise an issue for that if there isn't one, or is it just
> considered to be one aspect of the "externals are awful" meta-bug? :-)
I think it's just the "externals are awful" meta-bug.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Externals broken for https: or port 81 [was: Externals in Spanish
Translation?]
Posted by Julian Foad <ju...@btopenworld.com>.
Philip Martin wrote:
> Besides the cosmetic uglyness of our svn:externals, it doesn't work
> properly for anyone using using https:// or port 81 :-(
That sounds like something that should be in the issue tracker. Please
could you raise an issue for that if there isn't one, or is it just
considered to be one aspect of the "externals are awful" meta-bug? :-)
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals in Spanish Translation?
Posted by Philip Martin <ph...@codematters.co.uk>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> What's with the new svn:externals in the spanish translation?
>
> Is there really a need to have everyone check out two copies of the
> tools directory whenever they check out the tree? Plus, the externals
> are annoying in and of themselves, I hate seeing a "Performing status
> on external item at..." line whenever I run 'svn status' and there's
> no modifications.
Besides the cosmetic uglyness of our svn:externals, it doesn't work
properly for anyone using using https:// or port 81 :-(
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals clutter "svn status" output [was: Externals in Spanish
Translation?]
Posted by Julian Foad <ju...@btopenworld.com>.
I (Julian Foad) wrote:
> kfogel@collab.net wrote:
>> Yes, but let's also keep in mind that's a separate issue from the
>> current one. Even if svn:externals were better, we still wouldn't
>> want to be using them in the translations directory.
>
> Agreed. That's why I changed the Subject line :-)
... but maybe just changing the Subject line wasn't enough to indicate
clearly that I was raising a separate issue rather than claiming that
this is the proper interpretation of the original issue. I'll try to be
clearer next time.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals clutter "svn status" output [was: Externals in Spanish
Translation?]
Posted by Julian Foad <ju...@btopenworld.com>.
kfogel@collab.net wrote:
> Julian Foad <ju...@btopenworld.com> writes:
>
>>If the output of "svn status" is cluttered when externals are in use,
>>then that is a problem and we should unclutter it. Yes? (One can
>>always use "svn status --verbose" to check whether it is actually
>>traversing the externals if one is not sure.)
>
> Yes, but let's also keep in mind that's a separate issue from the
> current one. Even if svn:externals were better, we still wouldn't
> want to be using them in the translations directory.
Agreed. That's why I changed the Subject line :-)
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals clutter "svn status" output [was: Externals in Spanish Translation?]
Posted by kf...@collab.net.
Julian Foad <ju...@btopenworld.com> writes:
> If the output of "svn status" is cluttered when externals are in use,
> then that is a problem and we should unclutter it. Yes? (One can
> always use "svn status --verbose" to check whether it is actually
> traversing the externals if one is not sure.)
Yes, but let's also keep in mind that's a separate issue from the
current one. Even if svn:externals were better, we still wouldn't
want to be using them in the translations directory.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals clutter "svn status" output [was: Externals in Spanish
Translation?]
Posted by Julian Foad <ju...@btopenworld.com>.
Michael W Thelen wrote:
> Julian Foad wrote:
>> If the output of "svn status" is cluttered when externals are in use,
>> then that is a problem and we should unclutter it. Yes? (One can
>> always use "svn status --verbose" to check whether it is actually
>> traversing the externals if one is not sure.)
>
> Yes yes yes. Even "svn status -q" doesn't shut the dang thing up. :-)
> By the way, this is issue #1935.
Thanks for giving the issue number. This aspect ("-q" not shutting the
dang thing up) of that issue should be really easy to fix, and I can't
see many objections being raised even though it does change the console
output.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals clutter "svn status" output [was: Externals in Spanish
Translation?]
Posted by Michael W Thelen <th...@cs.utah.edu>.
Julian Foad wrote:
> Garrett Rooney wrote:
>> Plus, the externals are annoying in and of themselves, I hate seeing a
>> "Performing status on external item at..." line whenever I run 'svn
>> status' and there's no modifications.
>
> If the output of "svn status" is cluttered when externals are in use,
> then that is a problem and we should unclutter it. Yes? (One can
> always use "svn status --verbose" to check whether it is actually
> traversing the externals if one is not sure.)
Yes yes yes. Even "svn status -q" doesn't shut the dang thing up. :-)
By the way, this is issue #1935.
--
Michael W Thelen
It is a mistake to think you can solve any major problems just with
potatoes. -- Douglas Adams
Re: Externals clutter "svn status" output [was: Externals in Spanish Translation?]
Posted by "C. Michael Pilato" <cm...@collab.net>.
Julian Foad <ju...@btopenworld.com> writes:
> Garrett Rooney wrote:
> > Plus, the externals are annoying in and of themselves, I hate seeing
> > a "Performing status on external item at..." line whenever I run
> > 'svn status' and there's no modifications.
>
> If the output of "svn status" is cluttered when externals are in use,
> then that is a problem and we should unclutter it. Yes? (One can
> always use "svn status --verbose" to check whether it is actually
> traversing the externals if one is not sure.)
Actually, I've been meaning to bang out support for --no-externals in
all the subcommands that "do something" with externals. Passing this
flag to status, update, checkout, commit, etc. would prevent externals
processing from happening. I wonder if I remembered to file an issue
for this...?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals clutter "svn status" output [was: Externals in Spanish Translation?]
Posted by "C. Michael Pilato" <cm...@collab.net>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> That would make sense to me. It would make them at least somewhat
> less annoying, although honestly there are deeper issues that will
> still keep me from using them myself.
Oh, you're preaching to the converted, homey.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Externals clutter "svn status" output [was: Externals in Spanish
Translation?]
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Julian Foad wrote:
> Garrett Rooney wrote:
>
>> Plus, the externals are annoying in and of themselves, I hate seeing a
>> "Performing status on external item at..." line whenever I run 'svn
>> status' and there's no modifications.
>
>
> If the output of "svn status" is cluttered when externals are in use,
> then that is a problem and we should unclutter it. Yes? (One can
> always use "svn status --verbose" to check whether it is actually
> traversing the externals if one is not sure.)
That would make sense to me. It would make them at least somewhat less
annoying, although honestly there are deeper issues that will still keep
me from using them myself.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Externals clutter "svn status" output [was: Externals in Spanish
Translation?]
Posted by Julian Foad <ju...@btopenworld.com>.
Garrett Rooney wrote:
> Plus, the externals
> are annoying in and of themselves, I hate seeing a "Performing status on
> external item at..." line whenever I run 'svn status' and there's no
> modifications.
If the output of "svn status" is cluttered when externals are in use,
then that is a problem and we should unclutter it. Yes? (One can
always use "svn status --verbose" to check whether it is actually
traversing the externals if one is not sure.)
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org