The latest release of TomatoUSB still doesn't ship with IPv6 enabled even though it's "supported." I think that's actually the version I'm using right now. It hasn't been any better. http://www.4shared.com/dir/v1BuINP3/Toastman_Builds.html gives no useful information what so ever, and the Victek mods also mention nothing about IPv6.
I think you have to consider the official Tomato distribution from Jonathan Zarate as the kernel. There are other "branch" distros of Tomato which have evolved far past what the kernel version is. When I researched them, they're not forks, they're really just branches from the original master copy literally out of the same repo. Tomato USB is kind of the lead for the new development efforts and upgrades, but Victek RAF and Toastman share code with each other to customize to their own preferences. They're based on Tomato USB, which is based on Tomato. I run Victek on a WRT54GL and Toastman on an Asus RT-N16. They're both as rock solid as the kernel, core version. Other versions are outlined on the wikipedia page: https://en.wikipedia.org/wiki/Tomato_%28firmware%29
We still have 3 (2 in use) WRT54g Linksys routers running DD-WRT. one as primary and one set as a repeater at the back of the house...
DD-WRT is amazing, and it is sad that these open source firmwares seem to be dying... I'm due for a hardware upgrade, and it might just have to be to one of the sexy Apple routers...
I usually start my router shopping by popping open the DD-WRT Wiki up and making sure that I'm picking up a model that they have recent support for. I've had decent luck picking up routers that aren't explicitly branded as "OPEN SOURCE!" but have decent RAM and good buzz on the DD-WRT boards.
Frankly, I have never cared about adding comment number into the patch name because I never know what comment number I will have until I have actually added the comment. :)
For d.o issues with several patch iterations, it's common practice to append the comment number to each uploaded patch. I've always found this super useful to compare patch iterations and get a sense of chronology.
--> [issue_number]-[issue_description]-[comment-number].patch
Maybe a 2nd argument to your "branch-diff" command ?
Just a general suggestion about shell scripting: use $() for command substitution instead of back-quotes, the former can be nested without problems, and always quote stuff; for instance the last alias would be more robustly written as:
branch-diff = !git format-patch --stdout "$1" > "$(git cd-root)$(git branch-name).patch"
I think git forbids white spaces in branches names, so in this particular case the result is equivalent, but good practices never hurt.
Yeah my original instructions said to use git config --global to add the aliases, but since they're complex, I had problems adding them that way rather than just editing ~/.gitconfig.
I should have noted that I have *.patch files ignored in my ~/.gitignore so my repos aren't cluttered by patches. I figure if I have to add a patch to a repo I should add them manually anyway.
If you found this post early, I had to make some corrections:
1. Edit your ~/.gitconfig file directly. Don't add these aliases via the command line - it doesn't work.
2. The cd-root alias actually works now.
Only the fieldset container outputs markup that we wouldn't want if there were no accessible elements inside of it. I don't think (TM) this would have too much impact but it would be something to keep in mind while adding that.
It's my understanding that show() and hide() are more theming-oriented and the 'easy' functions without having to mess with array internals. You would use show() and hide() on an element that a user already has access to and would be normally visible.
The language isn't undefined. 'und' is the ISO language code for 'Undetermined' which is more useful and accurate than using an empty string like we did with Drupal 6.
More precisely, since there can be values of the field for the object in several languages (field translation - see Gabor's blog post :
this function returns the values that would be displayed given the current language settings.
The latest release of TomatoUSB still doesn't ship with IPv6 enabled even though it's "supported." I think that's actually the version I'm using right now. It hasn't been any better. http://www.4shared.com/dir/v1BuINP3/Toastman_Builds.html gives no useful information what so ever, and the Victek mods also mention nothing about IPv6.
I think you have to consider the official Tomato distribution from Jonathan Zarate as the kernel. There are other "branch" distros of Tomato which have evolved far past what the kernel version is. When I researched them, they're not forks, they're really just branches from the original master copy literally out of the same repo. Tomato USB is kind of the lead for the new development efforts and upgrades, but Victek RAF and Toastman share code with each other to customize to their own preferences. They're based on Tomato USB, which is based on Tomato. I run Victek on a WRT54GL and Toastman on an Asus RT-N16. They're both as rock solid as the kernel, core version. Other versions are outlined on the wikipedia page: https://en.wikipedia.org/wiki/Tomato_%28firmware%29
We still have 3 (2 in use) WRT54g Linksys routers running DD-WRT. one as primary and one set as a repeater at the back of the house...
DD-WRT is amazing, and it is sad that these open source firmwares seem to be dying... I'm due for a hardware upgrade, and it might just have to be to one of the sexy Apple routers...
I usually start my router shopping by popping open the DD-WRT Wiki up and making sure that I'm picking up a model that they have recent support for. I've had decent luck picking up routers that aren't explicitly branded as "OPEN SOURCE!" but have decent RAM and good buzz on the DD-WRT boards.
We are working on improving the situation, see http://drupal.org/node/1232120#comment-4795532 and http://drupal.org/node/1232120#comment-4807340.
Hi, thanks for this tip. I just tried it, and the array I get returned, is a little different (output is from the dpm function):
0 (Array, 3 elements)
value (String, 5 characters ) Hello
format (NULL)
safe_value (String, 5 characters ) Hello
1 (Array, 3 elements)
value (String, 30 characters ) Hello again!
format (NULL)
safe_value (String, 36 characters ) Hello again! <some nasty code>
I guess, the structure of the array depends on the kind of field type you ask for.
You can also use this function to get fields from the user object, although you need to pass it a full user object as returned by user_load().
Frankly, I have never cared about adding comment number into the patch name because I never know what comment number I will have until I have actually added the comment. :)
For d.o issues with several patch iterations, it's common practice to append the comment number to each uploaded patch. I've always found this super useful to compare patch iterations and get a sense of chronology.
--> [issue_number]-[issue_description]-[comment-number].patch
Maybe a 2nd argument to your "branch-diff" command ?
Just a general suggestion about shell scripting: use
$()for command substitution instead of back-quotes, the former can be nested without problems, and always quote stuff; for instance the last alias would be more robustly written as:branch-diff = !git format-patch --stdout "$1" > "$(git cd-root)$(git branch-name).patch"
I think git forbids white spaces in branches names, so in this particular case the result is equivalent, but good practices never hurt.
Regards,
Antonio
Yeah my original instructions said to use git config --global to add the aliases, but since they're complex, I had problems adding them that way rather than just editing ~/.gitconfig.
I should have noted that I have *.patch files ignored in my ~/.gitignore so my repos aren't cluttered by patches. I figure if I have to add a patch to a repo I should add them manually anyway.
@Dave Reid: Were you using git config --global?
I keep a separate folder outside of my clones for patches.
If you found this post early, I had to make some corrections:
1. Edit your ~/.gitconfig file directly. Don't add these aliases via the command line - it doesn't work.
2. The cd-root alias actually works now.
|= is not the boolean OR operator, it's the bitwise OR operator.
Only the fieldset container outputs markup that we wouldn't want if there were no accessible elements inside of it. I don't think (TM) this would have too much impact but it would be something to keep in mind while adding that.
Sounds like a performance killer to me. But I could be wrong.
Excellent suggestions Moshe. Added 'em to the queue.
Excellent tip. Loveing HLKD7F. Some more ideas ...
drupal_render_cache_by_query
drupal_explode_tags
entity_uri
user_load_by_name
Thanks for the post.
Is there a convenient way to set the value of a field too, something like field_set_items() ?
Paul
It's my understanding that show() and hide() are more theming-oriented and the 'easy' functions without having to mess with array internals. You would use show() and hide() on an element that a user already has access to and would be normally visible.
Thanks for this tidbit ...
About hiding items you describes the key '#access', however functions show() and hide() manage the key '#printed'.
How are related both keys? ... Seemingly, '#printed' leads the last decision.
The language isn't undefined. 'und' is the ISO language code for 'Undetermined' which is more useful and accurate than using an empty string like we did with Drupal 6.
Thanks! I overlooked the usage in my tiny example at the end, so I've adjusted that to enforce that the constant should be used whenever possible.
Never use und, use LANGUAGE_NONE if you must.
More precisely, since there can be values of the field for the object in several languages (field translation - see Gabor's blog post :
this function returns the values that would be displayed given the current language settings.
Just out curiosity: Why is the $node->language undefined and how do you set it to be defined, is there some documentation on this $node->language