Sponsored Content
The Lounge What is on Your Mind? Please Welcome Yoda (Bipin Ajith) to the Moderation Team Post 303038567 by Neo on Friday 6th of September 2019 10:24:24 AM
Old 09-06-2019
Please Welcome Yoda (Bipin Ajith) to the Moderation Team

Dear All,

Following our policy for forum moderators to have active LinkedIn profiles (and also to increase mod team diversity), please join me in congratulating the newest addition to our mod team, Yoda:

Bipin Ajith (Yoda)

Yoda has been hanging around unix.com for over eight years now and knows our unique forum customs and rules. He will add a lot of value as well as diversity to our moderation team!

Also, I want to thank all past moderators for their hard work moderating users, enforcing rules, adding tags of all kinds, and for their continued support to unix and linux users in daily technical Q&A.

We are all here for a noble cause, to help others help themselves.

As the old saying goes "give a person a fish and you feed them for a day; but teach them to fish and you help feed them for a lifetime...." That is what we do at unix.com, we do not do other's work for them nor do we write their code for them, we help guide them to write their own code and algorithms and help members learn to troubleshoot and configure (administer) their own systems, and we help them along the way in the spirit of shared community and learning new things together.

Welcome to the Mod Team, Yoda!
These 6 Users Gave Thanks to Neo For This Post:
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

Please Welcome Ravinder Singh to the Moderation Team

On this special Happy News Year day, 1 January 2019, I am pleased to promote Ravinder Singh to UNIX.COM Moderator, for at least the following reasons: Ravinder Loves UNIX.COM Ravinder has 1,372 Thanks, which puts him in the Top Ten in that important single category. Ravinder is one of... (8 Replies)
Discussion started by: Neo
8 Replies

2. What is on Your Mind?

Please Welcome Peasant to the Moderation Team

Dear All, Following our new policy for future forum moderators to have active LinkedIn profiles (and increase mod team diversity), please join me in congratulating our new addition to our mod team, Peasant: Peasant (Filip Skoblar) on LinkedIn Peasant is also an active moderator on our... (10 Replies)
Discussion started by: Neo
10 Replies

3. What is on Your Mind?

Please Welcome Akshay Hegde to the Moderation Team

Dear All, Following our policy for forum moderators to have active LinkedIn profiles (and also to increase mod team diversity), please join me in congratulating the newest addition to our mod team, Akshay Hegde: Akshay Hegde on LinkedIn Akshay has been very helpful to the site over the... (3 Replies)
Discussion started by: Neo
3 Replies
FSVS - URL format(5)						       fsvs						      FSVS - URL format(5)

NAME
Format of URLs - FSVS can use more than one URL; the given URLs are overlaid according to their priority. FSVS can use more than one URL; the given URLs are overlaid according to their priority. For easier managing they get a name, and can optionally take a target revision. Such an extended URL has the form ['name:'{name},]['target:'{t-rev},]['prio:'{prio},]URL where URL is a standard URL known by subversion -- something like http://...., svn://... or svn+ssh://.... The arguments before the URL are optional and can be in any order; the URL must be last. Example: name:perl,prio:5,svn://... or, using abbreviations, N:perl,P:5,T:324,svn://... Please mind that the full syntax is in lower case, whereas the abbreviations are capitalized! Internally the : is looked for, and if the part before this character is a known keyword, it is used. As soon as we find an unknown keyword we treat it as an URL, ie. stop processing. The priority is in reverse numeric order - the lower the number, the higher the priority. (See url__current_has_precedence() ) Why a priority? When we have to overlay several URLs, we have to know which URL takes precedence - in case the same entry is in more than one. (Which is not recommended!) Why a name? We need a name, so that the user can say 'commit all outstanding changes to the repository at URL x', without having to remember the full URL. After all, this URL should already be known, as there's a list of URLs to update from. You should only use alphanumeric characters and the underscore here; or, in other words, w or [a-zA-Z0-9_]. (Whitespace, comma and semicolon get used as separators.) What can I do with the target revision? Using the target revision you can tell fsvs that it should use the given revision number as destination revision - so update would go there, but not further. Please note that the given revision number overrides the -r parameter; this sets the destination for all URLs. The default target is HEAD. Note: In subversion you can enter URL@revision - this syntax may be implemented in fsvs too. (But it has the problem, that as soon as you have a @ in the URL, you must give the target revision every time!) There's an additional internal number - why that? This internal number is not for use by the user. It is just used to have an unique identifier for an URL, without using the full string. On my system the package names are on average 12.3 characters long (1024 packages with 12629 bytes, including newline): COLUMNS=200 dpkg-query -l | cut -c5- | cut -f1 -d' ' | wc So if we store an id of the url instead of the name, we have approx. 4 bytes per entry (length of strings of numbers from 1 to 1024). Whereas using the needs name 12.3 characters, that's a difference of 8.3 per entry. Multiplied with 150 000 entries we get about 1MB difference in filesize of the dir-file. Not really small ... And using the whole URL would inflate that much more. Currently we use about 92 bytes per entry. So we'd (unnecessarily) increase the size by about 10%. That's why there's an url_t::internal_number. Author Generated automatically by Doxygen for fsvs from the source code. Version trunk:2424 11 Mar 2010 FSVS - URL format(5)
All times are GMT -4. The time now is 01:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy