You are viewing an historical archive of past issues. Please
report new issues to the appropriate project issue tracker on
GitHub.
Comments
-
Greg Hurrell
Summary changed:
- From: Update to Git v<IP_ADDRESS>
- To: Update to Git v<IP_ADDRESS>
-
Greg Hurrell
Notes from <IP_ADDRESS> release announcement:
The latest maintenance release Git v<IP_ADDRESS> is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: a10c420e4d9152d6059f41825904cfac3062b135 git-<IP_ADDRESS>.tar.gz 41500708e87787d6139de413c4da91629aa79fa8 git-htmldocs-<IP_ADDRESS>.tar.gz 10151406ace1da92a70d203a7eb1c86024fdd919 git-manpages-<IP_ADDRESS>.tar.gz Also the following public repositories all have a copy of the v<IP_ADDRESS> tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v<IP_ADDRESS> Release Notes =========================== Fixes since v<IP_ADDRESS> --------------------- * The error message from "git push $there :bogo" (and its equivalent "git push $there --delete bogo") mentioned that we tried and failed to guess what ref is being deleted based on the LHS of the refspec, which we don't. * A handful of files and directories we create had tighter than necessary permission bits when the user wanted to have group writability (e.g. by setting "umask 002"). * "commit --amend" used to refuse amending a commit with an empty log message, with or without "--allow-empty-message". * "git commit --amend --only --" was meant to allow "Clever" people to rewrite the commit message without making any change even when they have already changes for the next commit added to their index, but it never worked as advertised since it was introduced in 1.3.0 era. * Even though the index can record pathnames longer than 1<<12 bytes, in some places we were not comparing them in full, potentially replacing index entries instead of adding. * "git show"'s auto-walking behaviour was an unreliable and unpredictable hack; it now behaves just like "git log" does when it walks. * "git diff", "git status" and anything that internally uses the comparison machinery was utterly broken when the difference involved a file with "-" as its name. This was due to the way "git diff --no-index" was incorrectly bolted on to the system, making any comparison that involves a file "-" at the root level incorrectly read from the standard input. * We did not have test to make sure "git rebase" without extra options filters out an empty commit in the original history. * "git fast-export" produced an input stream for fast-import without properly quoting pathnames when they contain SPs in them. * "git checkout --detach", when you are still on an unborn branch, should be forbidden, but it wasn't. * Some implementations of Perl terminates "lines" with CRLF even when the script is operating on just a sequence of bytes. Make sure to use "$PERL_PATH", the version of Perl the user told Git to use, in our tests to avoid unnecessary breakages in tests. Also contains minor typofixes and documentation updates. ---------------------------------------------------------------- Changes since v<IP_ADDRESS> are as follows: Alex Riesen (1): Restore umasks influence on the permissions of work tree created by clone Chris Webb (2): git-checkout: disallow --detach on unborn branch Allow edit of empty message with commit --amend Jay Soffian (1): fast-export: quote paths with spaces Jeff King (3): push: don't guess at qualifying remote refs on deletion add: create ADD_EDIT.patch with mode 0666 commit: fix "--amend --only" with no pathspec Junio C Hamano (10): show: fix "range implies walking" t/test-lib.sh: export PERL_PATH for use in scripts tests: enclose $PERL_PATH in double quotes t/README: add a bit more Don'ts diff-index.c: do not pretend paths are pathspecs diff-index.c: unify handling of command line paths diff-index.c: "git diff" has no need to read blob from the standard input rerere: make rr-cache fanout directory honor umask cache_name_compare(): do not truncate while comparing paths Git <IP_ADDRESS> Martin von Zweigbergk (1): add test case for rebase of empty commit Thomas Rast (1): Demonstrate git-show is broken with ranges Vincent van Ravesteijn (1): t: Replace 'perl' by $PERL_PATH -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to<EMAIL_ADDRESS>More majordomo info at http://vger.kernel.org/majordomo-info.html
-
Greg Hurrell
Summary changed:
- From: Update to Git v<IP_ADDRESS>
- To: Update to Git v<IP_ADDRESS>
-
Greg Hurrell
Notes from the <IP_ADDRESS> release announcement:
The latest maintenance release Git v<IP_ADDRESS> is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: 44013d9418ef23dd8bb67e80b27c9327356bfae8 git-<IP_ADDRESS>.tar.gz 8e19f56b2f484dc3327f1e8316c114dbe0ee2743 git-htmldocs-<IP_ADDRESS>.tar.gz d328241c130bbe38b12adf5702568c1edfff8623 git-manpages-<IP_ADDRESS>.tar.gz Also the following public repositories all have a copy of the v<IP_ADDRESS> tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v<IP_ADDRESS> Release Notes =========================== Fixes since v<IP_ADDRESS> --------------------- * The Makefile rule to create assembly output (primarily for debugging purposes) did not create it next to the source. * The code to avoid mistaken attempt to add the object directory itself as its own alternate could read beyond end of a string while comparison. * On some architectures, "block-sha1" did not compile correctly when compilers inferred alignment guarantees from our source we did not intend to make. * When talking to a remote running ssh on IPv6 enabled host, whose address is spelled as "[HOST]:PORT", we did not parse the address correctly and failed to connect. * git-blame.el (in compat/) have been updated to use Elisp more correctly. * "git checkout <branchname>" to come back from a detached HEAD state incorrectly computed reachability of the detached HEAD, resulting in unnecessary warnings. * "git mergetool" did not support --tool-help option to give the list of supported backends, like "git difftool" does. * "git grep" stopped spawning an external "grep" long time ago, but a duplicated test to check internal and external "grep" was left behind. Also contains minor typofixes and documentation updates. ---------------------------------------------------------------- Changes since v<IP_ADDRESS> are as follows: Heiko Voigt (1): link_alt_odb_entry: fix read over array bounds reported by valgrind Jeff King (1): checkout: don't confuse ref and object flags Jonathan Nieder (4): block-sha1: avoid pointer conversion that violates alignment constraints block-sha1: put expanded macro parameters in parentheses Makefile: fix location of listing produced by "make subdir/foo.s" Makefile: BLK_SHA1 does not require fast htonl() and unaligned loads Junio C Hamano (4): mergetool: support --tool-help option like difftool does Enumerate revision range specifiers in the documentation Prepare for <IP_ADDRESS> Git <IP_ADDRESS> Lawrence Mitchell (2): git-blame.el: Use with-current-buffer where appropriate git-blame.el: Do not use bare 0 to mean (point-min) Max Horn (1): Make <refname> documentation more consistent. Michael Schubert (1): Documentation/git-daemon: add missing word Ramkumar Ramachandra (1): commit: document a couple of options Ramsay Allan Jones (1): t7810-*.sh: Remove redundant test René Scharfe (1): git: Wrong parsing of ssh urls with IPv6 literals ignores port Rüdiger Sonderfeld (2): git-blame.el: use mapc instead of mapcar git-blame.el: Do not use goto-line in lisp code Štěpán Němec (1): doc: A few minor copy edits.
-
Greg Hurrell
Summary changed:
- From: Update to Git v<IP_ADDRESS>
- To: Update to Git v1.7.12
-
Greg Hurrell
Notes from the 1.7.12 release announcement:
The latest feature release Git v1.7.12 is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: 42ec1037f1ee5bfeb405710c83b73c0515ad26e6 git-1.7.12.tar.gz 50bbfeba77af9a411cc1a1e41220782cf3fd9b5e git-htmldocs-1.7.12.tar.gz fb572729ca5c60161dc651564a50d4378507e20f git-manpages-1.7.12.tar.gz Also the following public repositories all have a copy of the v1.7.12 tag and the master branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v1.7.12 Release Notes ========================= Updates since v1.7.11 --------------------- UI, Workflows & Features * Git can be told to normalize pathnames it read from readdir(3) and all arguments it got from the command line into precomposed UTF-8 (assuming that they come as decomposed UTF-8), in order to work around issues on Mac OS. I think there still are other places that need conversion (e.g. paths that are read from stdin for some commands), but this should be a good first step in the right direction. * Per-user $HOME/.gitconfig file can optionally be stored in $HOME/.config/git/config instead, which is in line with XDG. * The value of core.attributesfile and core.excludesfile default to $HOME/.config/git/attributes and $HOME/.config/git/ignore respectively when these files exist. * Logic to disambiguate abbreviated object names have been taught to take advantage of object types that are expected in the context, e.g. XXXXXX in the "git describe" output v1.2.3-gXXXXXX must be a commit object, not a blob nor a tree. This will help us prolong the lifetime of abbreviated object names. * "git apply" learned to wiggle the base version and perform three-way merge when a patch does not exactly apply to the version you have. * Scripted Porcelain writers now have access to the credential API via the "git credential" plumbing command. * "git help" used to always default to "man" format even on platforms where "man" viewer is not widely available. * "git clone --local $path" started its life as an experiment to optionally use link/copy when cloning a repository on the disk, but we didn't deprecate it after we made the option a no-op to always use the optimization. The command learned "--no-local" option to turn this off, as a more explicit alternative over use of file:// URL. * "git fetch" and friends used to say "remote side hung up unexpectedly" when they failed to get response they expect from the other side, but one common reason why they don't get expected response is that the remote repository does not exist or cannot be read. The error message in this case was updated to give better hints to the user. * "git help -w $cmd" can show HTML version of documentation for "git-$cmd" by setting help.htmlpath to somewhere other than the default location where the build procedure installs them locally; the variable can even point at a http:// URL. * "git rebase [-i] --root $tip" can now be used to rewrite all the history leading to "$tip" down to the root commit. * "git rebase -i" learned "-x <cmd>" to insert "exec <cmd>" after each commit in the resulting history. * "git status" gives finer classification to various states of paths in conflicted state and offer advice messages in its output. * "git submodule" learned to deal with nested submodule structure where a module is contained within a module whose origin is specified as a relative URL to its superproject's origin. * A rather heavy-ish "git completion" script has been split to create a separate "git prompting" script, to help lazy-autoloading of the completion part while making prompting part always available. * "gitweb" pays attention to various forms of credits that are similar to "Signed-off-by:" lines in the commit objects and highlights them accordingly. Foreign Interface * "mediawiki" remote helper (in contrib/) learned to handle file attachments. * "git p4" now uses "Jobs:" and "p4 move" when appropriate. * vcs-svn has been updated to clean-up compilation, lift 32-bit limitations, etc. Performance, Internal Implementation, etc. (please report possible regressions) * Some tests showed false failures caused by a bug in ecryptofs. * We no longer use AsciiDoc7 syntax in our documentation and favor a more modern style. * "git am --rebasing" codepath was taught to grab authorship, log message and the patch text directly out of existing commits. This will help rebasing commits that have confusing "diff" output in their log messages. * "git index-pack" and "git pack-objects" use streaming API to read from the object store to avoid having to hold a large blob object in-core while they are doing their thing. * Code to match paths with exclude patterns learned to avoid calling fnmatch() by comparing fixed leading substring literally when possible. * "git log -n 1 -- rarely-touched-path" was spending unnecessary cycles after showing the first change to find the next one, only to discard it. * "git svn" got a large-looking code reorganization at the last minute before the code freeze. Also contains minor documentation updates and code clean-ups. Fixes since v1.7.11 ------------------- Unless otherwise noted, all the fixes since v1.7.11 in the maintenance releases are contained in this release (see release notes to them for details). * "git submodule add" was confused when the superproject did not have its repository in its usual place in the working tree and GIT_DIR and GIT_WORK_TREE was used to access it. * "git commit --amend" let the user edit the log message and then died when the human-readable committer name was given insufficiently by getpwent(3).
-
Greg Hurrell
This is done on my development machines (see "Updating to Git 1.7.12").
Haven't done anything yet remotely.
-
Greg Hurrell
Status changed:
- From: new
- To: open
-
Greg Hurrell
Summary changed:
- From: Update to Git v1.7.12
- To: Update to Git v<IP_ADDRESS>
-
Greg Hurrell
v<IP_ADDRESS> is out:
The latest maintenance release Git v<IP_ADDRESS> is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: c5227b5202947bba3d63dca72662fad02d208800 git-<IP_ADDRESS>.tar.gz b42d5db34612825676d0a231cf9c566f8ad45e9f git-htmldocs-<IP_ADDRESS>.tar.gz 2d9c267c5370cdceb2e67f67abf5b152b0c18db9 git-manpages-<IP_ADDRESS>.tar.gz Also the following public repositories all have a copy of the v<IP_ADDRESS> tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git <IP_ADDRESS> Release Notes ========================== Fixes since v1.7.12 ------------------- * "git apply -p0" did not parse pathnames on "diff --git" line correctly. This caused patches that had pathnames in no other places to be mistakenly rejected (most notably, binary patch that does not rename nor change mode). Textual patches, renames or mode changes have preimage and postimage pathnames in different places in a form that can be parsed unambiguously and did not suffer from this problem. * "git cherry-pick A C B" used to replay changes in A and then B and then C if these three commits had committer timestamps in that order, which is not what the user who said "A C B" naturally expects. * "git commit --amend" let the user edit the log message and then died when the human-readable committer name was given insufficiently by getpwent(3). * Some capabilities were asked by fetch-pack even when upload-pack did not advertise that they are available. fetch-pack has been fixed not to do so. * "git diff" had a confusion between taking data from a path in the working tree and taking data from an object that happens to have name 0{40} recorded in a tree. * "git for-each-ref" did not correctly support more than one --sort option. * "git log .." errored out saying it is both rev range and a path when there is no disambiguating "--" is on the command line. Update the command line parser to interpret ".." as a path in such a case. * The "--topo-order", "--date-order" (and the lack of either means the default order) options to "rev-list" and "log" family of commands were poorly described in the documentation. * "git prune" without "-v" used to warn about leftover temporary files (which is an indication of an earlier aborted operation). * Pushing to smart HTTP server with recent Git fails without having the username in the URL to force authentication, if the server is configured to allow GET anonymously, while requiring authentication for POST. * The reflog entries left by "git rebase" and "git rebase -i" were inconsistent (the interactive one gave an abbreviated object name). * When "git push" triggered the automatic gc on the receiving end, a message from "git prune" that said it was removing cruft leaked to the standard output, breaking the communication protocol. * "git show --quiet" ought to be a synonym for "git show -s", but wasn't. * "git show --format='%ci'" did not give timestamp correctly for commits created without human readable name on "committer" line. * "git send-email" did not unquote encoded words that appear on the header correctly, and lost "_" from strings. * The interactive prompt "git send-email" gives was error prone. It asked "What e-mail address do you want to use?" with the address it guessed (correctly) the user would want to use in its prompt, tempting the user to say "y". But the response was taken as "No, please use 'y' as the e-mail address instead", which is most certainly not what the user meant. * "gitweb" when used with PATH_INFO failed to notice directories with SP (and other characters that need URL-style quoting) in them. * When the user gives an argument that can be taken as both a revision name and a pathname without disambiguating with "--", we used to give a help message "Use '--' to separate". The message has been clarified to show where that '--' goes on the command line. * When the user exports a non-default IFS without HT, scripts that rely on being able to parse "ls-files -s | while read a b c..." started to fail. Protect them from such a misconfiguration. * The attribute system may be asked for a path that itself or its leading directories no longer exists in the working tree, and it is fine if we cannot open .gitattribute file in such a case. Failure to open per-directory .gitattributes with error status other than ENOENT and ENOTDIR should be diagnosed, but it wasn't. * After "gitk" showed the contents of a tag, neither "Reread references" nor "Reload" did not update what is shown as the contents of it, when the user overwrote the tag with "git tag -f". * "ciabot" script (in contrib/) has been updated with extensive documentation. * "git-jump" script (in contrib/) did not work well when diff.noprefix or diff.mnemonicprefix is in effect. * Older parts of the documentation described as if having a regular file in .git/refs/ hierarchy were the only way to have branches and tags, which is not true for quite some time. * A utility shell function test_seq has been added as a replacement for the 'seq' utility found on some platforms. * Compatibility wrapper to learn the maximum number of file descriptors we can open around sysconf(_SC_OPEN_MAX) and getrlimit(RLIMIT_NO_FILE) has been introduced for portability. * We used curl_easy_strerror() without checking version of cURL, breaking the build for versions before curl 7.12.0. * Code to work around MacOS X UTF-8 gotcha has been cleaned up. * Fallback 'getpass' implementation made unportable use of stdio API. * The "--rebase" option to "git pull" can be abbreviated to "-r", but we didn't document it. * It was generally understood that "--long-option"s to many of our subcommands can be abbreviated to the unique prefix, but it was not easy to find it described for new readers of the documentation set. * The synopsis said "checkout [-B branch]" to make it clear the branch name is a parameter to the option, but the heading for the option description was "-B::", not "-B branch::", making the documentation misleading. Also contains numerous documentation updates. ---------------------------------------------------------------- Changes since v1.7.12 are as follows: Adam Butcher (1): Fix '\ No newline...' annotation in rewrite diffs Adam Spiers (1): Add missing -z to git check-attr usage text for consistency with man page Andreas Schwab (1): Documentation/git-filter-branch: Move note about effect of removing commits Brandon Casey (2): t/t5400: demonstrate breakage caused by informational message from prune prune.c: only print informational message in show_only or verbose mode David Aguilar (2): gitk: Teach "Reread references" to reload tags gitk: Rename 'tagcontents' to 'cached_tagcontent' Eric S. Raymond (4): fast-import: document the --done option contrib/ciabot: Get ciabot configuration from git variables Improved documentation for the ciabot scripts. Make the ciabot scripts completely self-configuring in the normal case. Felipe Contreras (1): gitk: Avoid Meta1-F5 Heiko Voigt (2): Let submodule command exit with error status if path does not exist Documentation/CodingGuidelines: spell out more shell guidelines Jay Soffian (1): gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO Jeff King (29): diff: do not use null sha1 as a sentinel value do not write null sha1s to on-disk index fsck: detect null sha1 in tree entries include agent identifier in capability string docs: monospace listings in docbook output check-docs: mention gitweb specially check-docs: update non-command documentation list command-list: add git-sh-i18n command-list: mention git-credential-* helpers check-docs: factor out command-list check-docs: list git-gui as a command check-docs: drop git-help special-case check-docs: get documented command list from Makefile send-pack: fix capability-sending logic do not send client agent unless server does first parse_feature_request: make it easier to see feature values fetch-pack: mention server version with verbose output config: warn on inaccessible files gitignore: report access errors of exclude files attr: warn on inaccessible attribute files t5550: put auth-required repo in auth/dumb t5550: factor out http auth setup t/lib-httpd: only route auth/dumb to dumb repos t/lib-httpd: recognize */smart/* repos as smart-http t: test basic smart-http authentication t: test http access to "half-auth" repositories http: factor out http error code handling http: prompt for credentials on failed POST log: fix --quiet synonym for -s Joachim Schmitz (2): http.c: don't use curl_easy_strerror prior to curl-7.12.0 sha1_file.c: introduce get_max_fd_limit() helper Junio C Hamano (34): test: rename $satisfied to $satisfied_prereq test: allow prerequisite to be evaluated lazily config: "git config baa" should exit with status 1 t7406: fix misleading "rev-parse --max-count=1 HEAD" sane_execvp(): ignore non-directory on $PATH Documentation: do not mention .git/refs/* directories receive-pack: do not leak output from auto-gc to standard output sh-setup: protect from exported IFS fetch-pack: do not ask for unadvertised capabilities send-email: validate & reconfirm interactive responses rev-list docs: clarify --topo-order description gitcli: describe abbreviation of long options Documentation: update the introductory section git-config doc: unconfuse an example precompose-utf8: do not call checks for non-ascii "utf8" warn_on_inaccessible(): a helper to warn on inaccessible paths specifying ranges: we did not mean to make ".." an empty set mergetool: style fixes Prepare for <IP_ADDRESS> apply: compute patch->def_name correctly under -p0 doc: "git checkout -b/-B/--orphan" always takes a branch name split_ident_line(): make best effort when parsing author/committer line Document file-glob for "git checkout -- '*.c'" gitcli: formatting fix gitcli: contrast wildcard given to shell and to git Almost <IP_ADDRESS> Start preparing for <IP_ADDRESS> Git <IP_ADDRESS> Further merging down for <IP_ADDRESS> Further merging in preparation for <IP_ADDRESS> attr: failure to open a .gitattributes file is OK with ENOTDIR Git <IP_ADDRESS> Draft release notes to <IP_ADDRESS> Git <IP_ADDRESS> Kacper Kornet (2): t6300: test sort with multiple keys for-each-ref: Fix sort with multiple keys Martin von Zweigbergk (4): add tests for 'git rebase --keep-empty' teach log --no-walk=unsorted, which avoids sorting demonstrate broken 'git cherry-pick three one two' cherry-pick/revert: respect order of revisions to pick Matthieu Moy (1): setup: clarify error messages for file/revisions ambiguity Michael Haggerty (1): git-config.txt: fix example Michael J Gruber (6): test-lib: provide case insensitivity as a prerequisite t0050: use the CASE_INSENSITIVE_FS test prereq t0050: use the SYMLINKS test prereq test-lib: provide UTF8 behaviour as a prerequisite rebase -i: use full onto sha1 in reflog t3910: use the UTF8_NFD_TO_NFC test prereq Michał Kiedrowicz (1): tests: Introduce test_seq Miklos Vajna (1): man: git pull -r is a short for --rebase Mischa POSLAWSKY (1): git-jump: ignore (custom) prefix in diff mode Nguyễn Thái Ngọc Duy (1): read_index_from: remove bogus errno assignments Paul Gortmaker (1): apply: delete unused deflate_origlen from patch struct Phil Hord (2): test: git-stash conflict sets up rerere stash: invoke rerere in case of conflict Philip Oakley (1): Doc: Improve shallow depth wording Ramkumar Ramachandra (1): t/perf: add "trash directory" to .gitignore Ramsay Allan Jones (1): test-regex: Add a test to check for a bug in the regex routines Robin Rosenberg (1): cleanup precompose_utf8 Stefan Zager (1): Make 'git submodule update --force' always check out submodules. Stephen Boyd (1): send-email: initial_to and initial_reply_to are both optional Thomas Rast (3): send-email: improve RFC2047 quote parsing diff_setup_done(): return void merge-recursive: eliminate flush_buffer() in favor of write_in_full() Wesley J. Landaker (1): Documentation: indent-with-non-tab uses "equivalent tabs" not 8 Yacine Belkadi (1): completion: add --no-edit to git-commit
-
Greg Hurrell
Summary changed:
- From: Update to Git v<IP_ADDRESS>
- To: Update to Git v<IP_ADDRESS>
-
Greg Hurrell
<IP_ADDRESS> release announcement:
The latest maintenance release Git v<IP_ADDRESS> is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: 277b759139ddb62c6935da37de8a483e2c234a97 git-<IP_ADDRESS>.tar.gz<PHONE_NUMBER>c7478b2339a1d87aa894bc4d2f5d6b git-htmldocs-<IP_ADDRESS>.tar.gz 8cf6fd255e83226b4abcdcd68dcf315c1995fd92 git-manpages-<IP_ADDRESS>.tar.gz Also the following public repositories all have a copy of the v<IP_ADDRESS> tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git <IP_ADDRESS> Release Notes ========================== Fixes since v<IP_ADDRESS> --------------------- * When "git am" is fed an input that has multiple "Content-type: ..." header, it did not grok charset= attribute correctly. * Even during a conflicted merge, "git blame $path" always meant to blame uncommitted changes to the "working tree" version; make it more useful by showing cleanly merged parts as coming from the other branch that is being merged. * "git blame MAKEFILE" run in a history that has "Makefile" but not "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got confused on a case insensitive filesystem and failed to do so. * "git fetch --all", when passed "--no-tags", did not honor the "--no-tags" option while fetching from individual remotes (the same issue existed with "--tags", but combination "--all --tags" makes much less sense than "--all --no-tags"). * "git log/diff/format-patch --stat" showed the "N line(s) added" comment in user's locale and caused careless submitters to send patches with such a line in them to projects whose project language is not their language, mildly irritating others. Localization to the line has been disabled for now. * "git log --all-match --grep=A --grep=B" ought to show commits that mention both A and B, but when these three options are used with --author or --committer, it showed commits that mention either A or B (or both) instead. * The subcommand to remove the definition of a remote in "git remote" was named "rm" even though all other subcommands were spelled out. Introduce "git remote remove" to remove confusion, and keep "rm" as a backward compatible synonym. Also contains a handful of documentation updates. ---------------------------------------------------------------- Changes since v<IP_ADDRESS> are as follows: Dan Johnson (1): fetch --all: pass --tags/--no-tags through to each remote David Gould (1): run-command.c: fix broken list iteration in clear_child_for_cleanup Felipe Contreras (1): completion: fix shell expansion of items Jeff King (4): argv-array: add pop function argv-array: fix bogus cast when freeing array fetch: use argv_array instead of hand-building arrays Revert "completion: fix shell expansion of items" Jens Lehmann (1): submodule: use argv_array instead of hand-building arrays Jeremy White (1): Documentation: describe subject more precisely Jonathan "Duke" Leto (1): Improve the description of GIT_PS1_SHOWUPSTREAM Junio C Hamano (11): mailinfo: strip "RE: " prefix blame $path: avoid getting fooled by case insensitive filesystems blame: allow "blame file" in the middle of a conflicted merge grep: teach --debug option to dump the parse tree log --grep/--author: honor --all-match honored for multiple --grep patterns log: document use of multiple commit limiting options grep.c: mark private file-scope symbols as static mailinfo: do not concatenate charset= attribute values from mime headers grep.c: make two symbols really file-scope static this time Start preparation for <IP_ADDRESS> Git <IP_ADDRESS> Michael J Gruber (6): grep: show --debug output only once t7810-grep: bring log --grep tests in common form t7810-grep: test multiple --grep with and without --all-match t7810-grep: test multiple --author with --all-match t7810-grep: test interaction of multiple --grep and --author options t7810-grep: test --all-match with multiple --grep and --author options Nguyễn Thái Ngọc Duy (3): remote: prefer subcommand name 'remove' to 'rm' doc: move rev-list option -<n> from git-log.txt to rev-list-options.txt Revert diffstat back to English Ralf Thielow (1): l10n: de.po: correct translation of a 'rebase' message Stefan Naewe (1): ls-remote: document the '--get-url' option Stephen Boyd (1): Documentation: Document signature showing options Thynson (2): l10n: Unify the translation for '(un)expected' l10n: Improve many translation for zh_CN
-
Greg Hurrell
Summary changed:
- From: Update to Git v<IP_ADDRESS>
- To: Update to Git v<IP_ADDRESS>
-
Greg Hurrell
The latest maintenance release Git v<IP_ADDRESS> is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: a071f03f6aab76b283828db1fdedbedb90085eb5 git-<IP_ADDRESS>.tar.gz 6f976c27aab7250f1a35b2b002ac7a07c3266cf4 git-htmldocs-<IP_ADDRESS>.tar.gz 49584f0b72e4a13f9a4df771bbde9cf70f25d317 git-manpages-<IP_ADDRESS>.tar.gz Also the following public repositories all have a copy of the v<IP_ADDRESS> tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git <IP_ADDRESS> Release Notes ========================== Fixes since v<IP_ADDRESS> --------------------- * "git am" mishandled a patch attached as application/octet-stream (e.g. not text/*); Content-Transfer-Encoding (e.g. base64) was not honored correctly. * It was unclear in the documentation for "git blame" that it is unnecessary for users to use the "--follow" option. * A repository created with "git clone --single" had its fetch refspecs set up just like a clone without "--single", leading the subsequent "git fetch" to slurp all the other branches, defeating the whole point of specifying "only this branch". * "git fetch" over http had an old workaround for an unlikely server misconfiguration; it turns out that this hurts debuggability of the configuration in general, and has been reverted. * "git fetch" over http advertised that it supports "deflate", which is much less common, and did not advertise the more common "gzip" on its Accept-Encoding header. * "git receive-pack" (the counterpart to "git push") did not give progress output while processing objects it received to the puser when run over the smart-http protocol. * "git status" honored the ignore=dirty settings in .gitmodules but "git commit" didn't. Also contains a handful of documentation updates. ---------------------------------------------------------------- Changes since v<IP_ADDRESS> are as follows: Jeff King (3): receive-pack: redirect unpack-objects stdout to /dev/null receive-pack: send pack-processing stderr over sideband receive-pack: drop "n/a" on unpacker errors Junio C Hamano (3): git blame: document that it always follows origin across whole-file renames Start preparing for <IP_ADDRESS> Git <IP_ADDRESS> Linus Torvalds (1): mailinfo: don't require "text" mime type for attachments Orgad Shaneh (1): commit: pay attention to submodule.$name.ignore in .gitmodules Peter Krefting (1): l10n: Fix to Swedish translation Ralf Thielow (1): clone --single: limit the fetch refspec to fetched branch Ramkumar Ramachandra (1): submodule: if $command was not matched, don't parse other args Shawn O. Pearce (2): Revert "retry request without query when info/refs?query fails" Enable info/refs gzip decompression in HTTP client
-
Greg Hurrell
This ticket is getting out of control. Closing in favor of issue #2016 (which is about upgrading to Git <IP_ADDRESS>.
-
Greg Hurrell
Status changed:
- From: open
- To: closed
Add a comment
Comments are now closed for this issue.


We believe games are a great media and way to express and communicate. These have to be done with passion and quality which are things that are usually disrupted when business is put ahead of ideas and people who work on them. In our eyes projects, people and ideas are not assets and money. They're spirit and soul of a form of art.
These are links to projects made by others that we want to share with you.
word-grabber.com: generator tools for games like Scrabble.


Cheshire3 Configuration: Workflow |
Workflows can be configured to define a series of processing steps that are common to several Cheshire3 databases/systems, as an alternative to writing customised code for each.
Workflow Configuration Tutorial including examples and explanation.
Base wrapping tags for workflows; analagous to <process> and <preprocess> in Index configurations.
Contains an ordered list of objects.
The results of the first object is given to the second and so on down the chain.
It should be apparent that subsequent objects must be able to accept as input, the result of the previous.
A call to an object within the system. <object>s define the following attributes:
type [ mandatory ]
Specifies the type of the object within the Cheshire3 framework.
Broadly speaking this may be a preParser, parser, database, recordStore, index, logger, transformer, workflow.
ref
A reference to a configured object within the system.
If unspecified, the current session is used to determine which server, database, recordStore and so forth should be used.
function
The name of the function to call.
If unspecified, the default function for the particular type of object is called.
For existing processing objects that can be used in these fields, see the object documentation.
Log text to a Logger object.
A reference to a configured Logger may be provided using the 'ref' attribute.
If no 'ref' attribute is present, the database's default logger is used.
Assign a specified value to a variable with a given name. Requires both of the following attributes:
from [ mandatory ]
the value to assign
to [ mandatory ]
a name to refer to the variable
Feed the current input into each processing fork.
[ more details to follow ]
Iterate/loop through the items in the input object.
Like <workflow> contains an ordered list of objects.
Each of the items in the input is run through the chain of processing objects.
Allows for error catching.
Any errors that occur within this element will not cause the workflow to exit with a failure.
Must be followed by an <except> element, which may also be followed by an <else> element.
Error handling.
This element must follow a <try> element.
Specifies action to take in the event of an error occuring within the preceeding <try>.
Success handling.
This element may follow a <try> <except> pair.
Specifies action to take in the event that no errors occur within the preceeding <try>.
Skip remaining processing steps, and move on to next iteration while inside a <for-each> loop element.
May not contain any further elements or attributes.
This can be useful in the error handling <except> element.
e.g. if a document cannot be parsed, it cannot be indexed, so skip to next document in the documentFactory.
Break out of a <for-each> loop element, skipping all subsequent processing steps, and all remaining iterations. May not contain any further elements or attributes.
Raise an error occuring within the preceeding <try> to the calling script or workflow. May only be used within an <except> element. May not contain any further elements or attributes.
Return the result of the previous step to the calling script or workflow. May not contain any further elements or attributes.


Command-line build saves me from checking in broken code. Thanks command-line build!
12/14/2009, 8:40:10 AM
Favs: 0
Retweets: 0
link--- layout: tweet ---
Command-line build saves me from checking in broken code. Thanks command-line build!
12/14/2009, 8:40:10 AM
Favs: 0
Retweets: 0
link


Genesis 24:21
And the man wondering at her held his peace, to wit whether the LORD had made his journey prosperous or not.


--- layout: archive title: Zulip Chat Archive permalink: /stream/113488-general/topic/substs.20and.20reflexivity.html ---
It seems like subst
solves a reflexive goal but substs
does not. If I replace subst p, subst q
with substs p q
, I have to add refl
to solve the goal.
Looking at the definition of the interactive subst
, I can see why:
meta def subst (q : parse texpr) : tactic unit := i_to_expr q >>= tactic.subst >> try (tactic.reflexivity reducible)
So the documentation on substs
is not quite correct:
/-- Multiple subst. `substs x y z` is the same as `subst x, subst y, subst z`. -/ meta def substs (l : parse ident*) : tactic unit := l.mmap' (λ h, get_local h >>= tactic.subst)
Is it enough to add >> try (tactic.reflexivity reducible)
to the end of the substs
definition to recoup this feature? Is there any reason why we shouldn't do this?
Last updated: Apr 24 2020 at 19:02 UTC


Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
IN THE HIGH COURT OF KERALA AT ERNAKULAM PRESENT: THE HONOURABLE MR.JUSTICE V.CHITAMBARESH WEDNESDAY, THE 19TH DAY OF AUGUST 2015/28TH SRAVANA, 1937 WP(C).No. 10608 of 2011 (A) ---------------------------- PETITIONER(S): ----------------- 1. VINOD GEORGE, S/O.A.M.GEORGE, AZHAKATHU HOUSE, NEAR THIRUVALLA RAILWAY STATION THIRUVALLA-689 111. 2. JOY THOMAS, S/O.K.K.THOMAS, KODIATTU HOUSE, EAST OF THIRUVALLA RAILWAY STATION THIRUVALLA-689 101. 3. SUSAMMA THOMAS, D/O.E.M.ZACHARIA, MANAYIL HOUSE, OPPOSITE THIRUVALLA RAILWAY, THIRUVALLA-689111. 4. JAMES THOMAS, S/O.E.T.THOMAS EDATHUMPARAYIL, PENSION KUNNU, THIRUVALLA-689111. 5. RENJI VARKEY, S/O.M.P.VARKEY, NEAR THIRUVALLA RAILWAY STATION, THIRUVALLA-689111. 6. GEORGE JOSHUA,S/O.JOSHUA VARGHESE, MOOLAYIL HOUSE, EAST OF THIRUVALLA RAILWAY STATION THIRUVALLA-689 105. 7. K.V.GEORGE,S/O.P.V.VARGHESE,PANDENPADAVIL NEAR THIRUVALLA RAILWAY STATION, THIRUVALLA PIN-689101. 8. P.A.ABRAHAM, S/O.P.V.ABRAHAM, PAYYAMPALLIL HOUSE, PENSION KUNNU, THIRUVALLA PIN-689111. 9. STANLY P.MATHEW,S/O.P.M.MATHEW, PEEDIKACHIRAYIL, EAST OF THIRUVALLA RAILWAY STATION THIRUVALLA-689101. 10. M.C.JOSEPH, S/O.M.C.CLITUS, SANTHI BHAVAN, EAST OF THIRUVALLA RAILWAY STATION THIRUVALLA-689101. BY ADVS.SRI.N.SUBRAMANIAM SRI.M.S.NARAYANAN SRI.P.T.GIRIJAN SMT.USHA NARAYANAN W.P (C) No.10608 of 2011 : 2 : RESPONDENT(S): ------------------- 1. UNION OF INDIA REPRESENTED BY ITS SECRETARY, MINISTRY OF RAILWAYS, RAIL BHAVAN NEW DELHI - 110 001. 2. THE GENERAL MANAGER SOUTHERN RAILWAY, PARK TOWN P.O., CHENNAI - 600 001. 3. THE DIVISIONAL MANAGER,SOUTHERN RAILWAY, THIRUVANANTHAPURAM-695001. 4. THE KERALA STATE POLLUTION CONTROL BOARD PARYAVARAN BHAVAN, THIRUVANANTHAPURAM-695001. 5. THE ENVIRONMENTAL ENGINEER,KERALA STATE POLLUTION CONTROL BOARD, DISTRICT OFFICE MAKKAMKKUNNU, PATHANAMTHITTA DISTRICT-689645. 6. THE DISTRICT COLLECTOR,PATHANAMTHITTA, COLLECTORATE, PATHANAMTHITTA-689645. R,R1 TO 3 BY ADV.  EXT.P2 TRUE COPY OF THE COMPLAINT MADE BY THE ACTION COUNCIL OF PATHANAMTHITTA DISTRICT RAILWAY PASSENGERS. EXT.P3 TRUE COPY OF THE COMPLAINT MADE BY THE ACTION COUNCIL PATHANAMTHITTA DISTRICT RAILWAY PASSENGERS. EXT.P4 TRUE COPY OF THE COMPLAINT MADE BY THE ACTION COUNCIL OF PATHANAMTHITTA DISTRICT RAILWAY PASSENGERS. EXT.P5 TRUE COPY OF THE MASS MEMORANDUM SUBMITTED BEFORE THE MINISTER IN CHARGE OF STATE POLLUTION CONTROL BOARD, TRIVANDRUM. EXT.P6 TRUE COPY OF THE MASS REPRESENTATION SUBMITTED BEFORE THE CHAIRMAN OF CENTRAL POLLUTION CONTROL BOARD, NEW DELHI. EXT.P7 TRUE COPY OF THE COMPLAINT FILED BY THE DISTRICT RAILWAY PASSENGERS ACTION COUNCIL BEFORE THE HUMAN RIGHTS COMMISSION, KERALA STATE. EXT.P8 TRUE COPY OF THE REPORT FILED BY THE ENGINEER OF POLLUTION CONTROL BOARD BEFORE THE KERALA STATE HUMAN RIGHTS COMMISSION. EXT.P9 TRUE COPY OF THE INTERIM ORDER PASSED BY THE KERALA STATE HUMAN RIGHTS COMMISSION. EXT.P10 TRUE COPY OF PHOTOGRAPH. EXT.P11 TRUE COPY OF PHOTOGRAPH. EXT.P12 TRUE COPY OF PHOTOGRAPH. EXT.P13 TRUE COPY OF THE LETTER PREFERRED BY THE RAILWAY RESIDENTS ASSOCIATION. EXT.P14 TRUE COPY OF THE ORDER PASSED BY THE KERALA STATE HUMAN RIGHTS COMISSION. EXT.P15. TRUE COPY OF THE NOTICE ISSUED BY THE ENVIRONMENT ENGINEER, OFFICE OF KERALA STATE POLLUTION CONTROL BOARD, PATHANAMTHITTA. EXT.P16 TRUE COPY OF LETTER WROTE BY THE THIRUVALLA MEDICAL MISSION HOSPITAL BEFORE THE MANAGER OF SOUTHERN RAILWAY. W.P(C) No.10608/2011 : 2 : EXT.P17 TRUE COPY OF THE LETTER SUDARSHAN NETHRA CHIKILSALAYAM. EXT.P18 TRUE COPY OF THE RESOLUTION ISSUED BY THE SECRETARY OF THIRUVALLA MUNICIPALITY ALONG WITH COVERING LETTER. EXT.P19 TRUE COPY OF THE COMMUNICATION OF AUGMENTATION OF GOODS HANDLING FROM 32 BCN WAGONS TO 41 BCN WAGONS. EXT.P20 TRUE COPY OF THE LETTER WROTE BY MR.P.J.KURIAN, M.P. TO THE MINISTER FOR RAILWAY. EXT.P21 TRUE COPY OF THE LETTER WROTE BY MR.P.J.KURIAN, M.P. TO THE G.M. SOUTHERN RAILWAY, CHENNAI. EXT.P22 TRUE COPY OF THE REPRESENTATION FILED BY MR.P.J.KURIAN, M.P. BEFORE THE MINISTER FOR RAILWAYS. EXT.P23 TRUE COPY OF THE REPORT OF THE POLLUTION CONTROL BOARD, DISTRICT OFFICE, PATHANAMTHITTA IN W.P.(C) NO.15219/09 EXT.P24 TRUE COPY OF THE JUDGMENT IN W.P.(C) NO.15219/09. RESPONDENT'S EXTS: EXT.R1(a) TRUE COPY OF LETTER DATED 28.6.2010 OF THE TRANSPORTATION BRANCH, HEADQUARTERS, SOUTHERN RAILWAY, CHENNAI ALONG WITH THE LETTERDATED 11.6.2010 OF RAILWAY BOARD. EXT.R1(b) TRUE COPY OF REPRESENTATION DATED 12.8.2009 SENT BY THE C.I. T.U. TALUK COMMITTEE, PATHANAMTHITTA. EXT.R1(c) TRUE COPY OF REPRESENTATION DATED 21.10.2009 OF KERALA STATE MERCHANTS ASSOCIATION, AREA COMMITTEE, THIRUVALLA. EXT.R1(d) TRUE COPY OF REPRESENTATION DATED 21.10.2009 OF ALL KERALA RAILWAY C & F AGENTS ASSOCIATION, THIRUVALLA UNIT TO THE THIRD RESPONDENT. EXT.R1(e) TRUE COPY OF INSTRUCTION DATED 10.7.2009. //TRUE COPY// P.S. TO JUDGE. V.CHITAMBARESH, J. --------------------- W.P (C) Nos. 10608/2011, 12995/2011 & 29211 of 2009 --------------------- Dated this the day 19th of August, 2015 J U D G M E N T
All these writ petitions are connected and I shall refer to the exhibits in W.P.(C) No.10608/2011 for the sake of convenience.
2. The Pathanamthitta District Railway Passenger Action Council had preferred Ext.P4 representation to the fifth respondent complaining of high risk pollution and environmental degradation in and around Thiruvalla Railway Station. The complaint highlighted the loading and unloading of cement bags on the platform causing serious health hazards to the passengers. The relevant part of Ext.P4 representation is extracted hereunder:-
"As you may be aware about 7000 passengers are travelling or making use of Tiruvalla Railway station every day.
Recently a goods siding is constructed just adjacent to the passenger platform. Presently in the siding a rake of cement wagons are unloaded on daily basis. Cement is the only commodity handled almost every day under the nose of the waiting passengers. Passengers are experiencing WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 2 serious health hazard as the cement- filled smoky air heavily pollutes the platforms and the entire nearby areas. This dangerous pollution is a silent killer and the passengers regularly using the Railway station are the worst affected."
The failure to take remedial steps by respondents 1 to 3 prompted the Action Council to move the Kerala State Human Rights Commission. The Commission by Ext.P14 order directed the fifth respondent to take steps under Section 22 (A) and 41 of the Air (Prevention and Control of Pollution) Act, 1981 against respondents 1 to 3. The fifth respondent even issued Ext.P15 notice to the third respondent indicating that the present activity causing pollution is a culpable offence punishable with imprisonment and fine. Every thing proved futile necessitating the Action Council and two other passengers to file WP (C) No.15219/2009 on the file of this Court. One of the reliefs in the writ petition pertained to the proposed construction of a cement yard at Thiruvalla Railway Station for the purpose of unloading of cement bags from the goods wagon. Relief (a) therein is extracted hereunder: WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 3 "(a) Issue a writ of prohibition or appropriate writ, order or direction commanding the railway authorities to restrain from going ahead with the proposed construction of the cement yard at Thiruvalla railway station for the purpose of unloading of cement bags from the goods wagons and transportation of the same into the lorries/other transportation vehicles."
3. The fifth respondent herein who was the fourth respondent in the said writ petition filed a report supporting the writ petition and confirming the pollution due to unloading of cement bags. The relevant part of Ext.P23 report is extracted hereunder:
"The Goods unloading platform at the Thiruvalla Railway Station is located adjacent to the main passenger platform (No.2). Several goods wagons carrying cement bags are regularly unloaded and loaded to trucks in this platform. Also, the cement from broken bags and refilled in open. This results in emanation of dust causing nuisance to the passengers and nearby residents.
There are a number of residential buildings within 100m radius of the cement handling area. No protective/control measures are taken WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 4 by the railway authorities to abate the air pollution/nuisance. Doors on both sides of the wagons are kept open during unloading to facilitate better working environment. Hence cross winds spreads cement dust to larger area. Continuous inhalation of cement dust may lead to serious bronchile problems."
There was every likelihood of the reliefs in the said writ petition being granted in the wake of the material then available on record. Respondents 1 to 3 thereupon undertook before this Court that they have no intention to construct a cement yard at Thiruvalla Railway Station and that the apprehension of the petitioners was misplaced. It is in view of the said stand taken by respondents 1 to 3 was the writ petition disposed of by Ext.P24 judgment and the operative part is extracted hereunder:-
5. ........ Having carefully perused the entire materials available on record, we are satisfied that no relief can be granted to the petitioners at this stage, since the respondents have categorically stated that they do not intend to construct a cement yard at Thiruvalla Railway Station. In that WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 5 view of the matter, especially in the light of the stand taken by the Railway authorities, the Writ Petition is closed."
4. The Government of Kerala in the meanwhile issued a notification dated 22.4.2009 (produced as Ext.P1 in WP(C) No. 29211/2009) under Section 4(1) of the Land Acquisition Act, 1894. The purpose stated therein was the doubling of railway track between Chengannur and Chingavanam for the southern railway. There can be no dispute that the same is a public purpose if it is solely for the purpose of doubling of track without expanding the goods platform (used also for unloading cement bags). The present exercise includes the augmentation of the goods platform increasing its capacity from 32 BCN wagons to 41 BCN wagons. This is evident from Ext.P19 communication issued by the second respondent to the President of the Vigilance Council formed. The relevant part of Ext.P19 communication reads as follows:
"VII) Cement Yard: The Railway Goods shed at
Thiruvalla has been serving the public requirement since long. It deals with WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 6 inward traffic of all commodities including cement. An average of 3 rakes of Cement per month is dealt with at the goods shed. The present capacity of the goods shed dealing with 32 BCN wagons is planned to be augmented to 41 BCN wagons."
5. An Advocate Commissioner was deputed in these three writ petitions who has filed a detailed report dated 10.8.2015 along with photographs and mahazar. The same reflects that a new goods platform of breadth 20 meters and length 650 meters is proposed to be constructed in the place of the old goods platform of breadth 10-13.25 meters and length 260 meters. The relevant part of the report of the Advocate Commissioner is extracted hereunder.
"The proposed goods platform is having a breadth of 20 meters in breadth and a length of 650 meters as against the old platform having a breadth of 10-13.25 meters in breadth and 260 meters in length. When the new platform is constructed the distance between the eastern end of the goods platform to the residential houses will be further reduced. The environmental engineer to the pollution control board opined that WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 7 if the new platform is constructed the distance between the goods platform and the houses will be considerably reduced and the risk of health hazard will also increase considerably."
The report of the Advocate Commissioner also throws light on the fact that houses are situated within a distance of 25 meters from the old goods platform and the respondents may have to land on the new goods platform (if constructed) when they step out of their house. It is not disputed before me that the exercise of unloading goods in the goods platform very much includes cement bags also as conceded in Ext.P19 communication.
6. The Thiruvalla Municipal Council has already passed Ext.P18 resolution condemning the move of respondents 1 to 3 to augment and shift the goods platform. That pollution still subsists due to the unloading of cement bags is conceded even in the counter affidavit filed by the sixth respondent District Collector . The relevant part of the counter affidavit filed by the District Collector is extracted hereunder:
WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 8 "It is hereby submitted that the functioning of the cement yard at the Thiruvalla Railway Station is causing nuisance, air pollution and inconveniences to the passengers as well as nearby residents. The cement yard is situated adjacent to the passenger plat form No.2 of Thiruvalla Railway Station. Cement bag are being unloaded and then loaded into the Lorries directly from the wagons. At the time of the above mentioned unloading and loading, cement dust emanates. Pollution/disturbance is very high while handling of broken bags and at the time of cleaning the wagons after unloading the cement bags. Pollution control Board found that cement dust was spreading around area including the passenger plat form Nos. 1 & 2. There are large number of residential houses within a radius of 100 m from the cement yard. The cement yard is an open area and no preventive measures have been taken by the Railway Authorities to prevent air pollution at the time of cement handling. At the time of unloading cement bags from the railway wagons, both sides of the wagon are kept open and the cross winds spreads the dust to the nearby areas leading to respiratory ailments to the nearby residents." WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 9 Thus all the authorities namely the District collector, Thiruvalla Municipality, Pollution Control Board and the passengers are disgusted with the loading and unloading activity of cement bags in the goods platform.
7. No doubt the fifth respondent has been repeatedly suggesting methods to abate even the existing nuisance and pollution in the old goods platform. Ext.P8 report, Ext.P23 report as well as the two reports filed in this writ petition suggest the construction of another pucca building with roof and dust extraction system. Respondents 1 to 3 in the counter affidavit dated 20.7.2012 filed in the writ petition have already declared that all these remedial measures are incapable of being executed. The relevant part of the counter affidavit of respondents 1 to 3 is extracted hereunder:
"Regarding the recommendations of Pollution Control Board and Human Rights Commission, it is humbly submitted that, due to the forthcoming doubling works and the resultant provision of overhead Electrical equipment, it will not be feasible to WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 10 fully cover up the goods area (about 600 Mts length) by way of complete roofing of the same. Besides, it is respectfully submitted that, nowhere in Indian Railways the air pollution control facilities such as dust extraction facility with water scrubber and chimney are available. The ground areas will be asphalted as in vogue in the Goods Shed areas elsewhere. It is further submitted that almost all goods sheds available in the country are in thickly populated areas, and the shifting of these goods shed to some remote places is not practical and it is neither the interest of the public nor the interest of the country."
A goods shed is entirely different from a goods platform which can only be constructed far away from the passenger platform. The dimension of the goods platform (particularly when goods include cement bags also) cannot be altered or changed in view of the specific stand taken in Ext.P24 judgment. Respondents 1 to 3 cannot approbate and reprobate and take inconsistent stands depending on the case or the court. Taking inconsistent pleas by a party makes its conduct far from satisfactory and the parties cannot blow hot WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 11 and cold by taking by taking such inconsistent stand. It has been so held in Air Line Pilots' Association of India v. DG of Civil Aviation [2011 (5) SCC 435] which has been followed by a Division Bench of this Court in Kerala Transport Development Finance Corporation Ltd. and another v. Basil T.K. and others [2012 (2) KHC 33]. To the same effect are the decisions in Karam Kapahi and others v. Lal Chand Public Charitable Trust and another [(2010) 4 SCC 753] and Mumbai International Airport Private Limited and another v. Golden Chariot Airport and another [(2010) 10 SCC 422]. Having undertaken in unequivocal terms that there is no proposal to construct a cement yard in Ext.P24 judgment, respondents 1 to 3 cannot thereafter indulge in the same under the guise of line doubling.
8. Even the storing, loading and unloading of cement in a shopping complex has been held to be abnoxious and violative of the right to life in Antony v. Commissioner, Corporation of Cochin [1994 (1) KLT 169]. The following observations therein are apposite.
"10. As regards the contention of the petitioner based on the right to life guaranteed under Art. 21 of the WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 12 Constitution of India it has to be noted that by a catena of decisions of the Supreme Court and High Courts, the expression "life" occurring in Art.21 is given an expanded meaning and under the expanded meaning, the right to pure drinking water, pollution free air, and right to good roads, etc. have all been held to be the facet of right to life guaranteed under Art.21 of the Constitution of India. The expression "life" no longer means mere animal existence or continued drudgery, but includes the finer graces of human civilisation: vide - AIR 1984 SC 74/79 Dr. P. Nalla Thampy Thera V. Union of India and others) and courts have residual power not only to enforce the fundamental purpose of law but also the moral welfare of the State and its subject. (see supra). Compelling citizens to inhale obnoxious dust (fine powder of asbastos which can lead to a serious form of lung disease 'asbestosis' amounts to deprivation of his life though the process of deprivation may not be quick yet it is slow but certain. Forcing a person to live in sub-human conditions also amounts to the taking away of their life, not by execution of death WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 13 sentence, but by slow and gradual process by robbing him of his human qualities and graces, a process which is more cruel than sending a man to the gallows. To convert human existence into animal existence no doubt amounts to taking away human life, because a man lives only by this mere physical existence or by bread alone, but by his human existence. (See in this connection the observation of the Supreme Court in Olga Tellis's case - AIR 1986 SC 180 followed in Sankar v. Durgapur Projects (AIR 1988 Cal.136) where it was held that to force a man to live with his family in only a small room of a two rooms quarter and to share bath, toilet and kitchen with another family is violative of his fundamental right guaranteed under Art.21 of the Constitution of India. In Santhilal & Company v. Bombay (AIR 1989 Bom.226) the Bombay High Court upheld the validity of Bombay Metropolitan Regions Specified Commodities Markets (Regulations and Location) Act, 1983 which is an environmental legislation providing for shifting of iron and steel trade from Bombay to a new market yard."
WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 14 Passengers are expected to enjoy a pollution free travel and the residents nearby cannot also be tormented by open use of the goods platform. It is now brought out that the notification under Section 4(1) of the Land Acquisition Act dated 17.7.2009 has been followed by a declaration under Section 6 thereof on 22.4.2010. But no document has been produced before me by anybody to show that an Award under Section 11 of the Land Acquisition Act, 1894 has hitherto been passed. I quash Ext.P1 notification in W.P.(C) No.29211/2009 and all further proceedings pursuant thereto in so far as it relates to the expansion of the existing goods platform at Thiruvalla Railway Station. In other words, the doubling of railway track can go on and the present goods platform can also be shifted to another spot provided its dimension is not changed or its activity augmented. Respondents 4 and 5 are also directed to see to it that even the existing activity does not cause any pollution or other health hazards to the passengers or the residents nearby. The respondents are also free to limit the area of acquisition when the dimension of the existing goods WP(C) Nos.10608/2011, 12995/2011 & 29211 of 2009 15 platform is not to be altered even if shifted.
The Writ Petitions are allowed. No costs.
Sd/-
V.CHITAMBARESH, Judge.
nj.


{{ partial "app_header" . }} {{ $nextRunTimeLength := len .Context.NextRunTimes }} {{ if eq $nextRunTimeLength 0 }}
We will use this email address to send you the updates
We will use this name to address you in the email
{{ if eq $count 0 }}We suggest to select 08 hrs or 17hrs depending on when you have free time{{end}}
Select atleast one hour of the day receive notifications
{{ if eq $count 0 }}We suggest you select Monday through Thursday{{end}}
Select atleast one day of week to receive notifications
Load from System Time Note: TimeZone Offset is calculated from the browser. NOTE: Use TimeZone name to consider Daylight Savings changes
Can't find your timezone? Load All TimeZones or Load based on Offset
Slack Configuration and Webhooks currently supported


A GRIB Collection is a collection of files that have GRIB records in them. Each file will have a grib index (gbx9) file generated for it. Once generated, gbx9 files never have to be redone.
Each logical collection has a CDM index (ncx2) file. All the records for a single runtime comprise a logical collection, called a RC.
<dataset name="GRIB Collection Example for tutorial (single runtime)" serviceName="gribServices" > <featureCollection name="Ismoro Single Runtime" featureType="GRIB1" harvest="true" path="Grib/srt"> <collection name="collsrt" spec="/machine/tds/data/grib/ecmwf/.*grib$" /> <update startup="test" /> </featureCollection> </dataset>Single RC dataset, single CDM index file. One time dimension. May have multiple groups (horizontal domains).
<dataset name="GRIB Collection Example for tutorial (multiple runtimes)" serviceName="gribServices"> <featureCollection name="GFS multiple runtime" featureType="GRIB2" harvest="true" path="Grib/mrt"> <collection name="collmrt" spec="/machine/tds/data/grib/gfsmrt/.*grib2$" /> <update startup="test" /> </featureCollection> </dataset>One RC dataset for each runtime, plus PofGC "collection dataset" with both runtime and time dimensions.
<dataset name="GRIB Collection Example for tutorial (file partition)" serviceName="gribServices"> <featureCollection name="GFS file partition" featureType="GRIB2" harvest="true" path="Grib/fp"> <collection name="collfp" spec="/machine/tds/data/grib/gfsfp/.*grib2$" timePartition="file"/> <update startup="test" /> </featureCollection> </dataset>One RC dataset for each runtime, plus PofGC "collection dataset" with both runtime and time dimensions. More efficient indexing.
<dataset name="GRIB Collection Example for tutorial (directory partition)" serviceName="gribServices">
<featureCollection name="GFS file partition" featureType="GRIB1" harvest="true" path="Grib/dp">
<collection name="colldp" spec="/machine/tds/data/grib/rfc/**/.*grib1$" timePartition="directory"/>
<update startup="test" />
</featureCollection>
</dataset>
One RC dataset for each runtime, plus PofGC or PofP "collection dataset" for each directory in the tree. Scales to large collections.
One RC dataset for each runtime, plus PofGC or PofP "collection dataset" for each directory in the tree. Scales to large collections. More efficient indexing.
{collection} -> {runTime} -> {Group} : a RC is a single runtime with 1 or more groups (GDS), has a single index (ncx2) file.
PofGC = {RC}
PofP = {PofGC}


You get full help with health costs
Anyone who gets {{bentype}}; or is named on your claim, gets free:
- NHS prescriptions
- NHS dental treatment
- NHS Sight tests
- NHS wigs and fabric supports
They'll also get help towards the cost of:
- new glasses or contact lenses
What you'll need as proof
You may have to show proof you get {{bentype}}.
You can use your Statement of Benefits as proof. You can get a copy of this letter by calling Jobcentre Plus.
Telephone: 0345 608 8545
Textphone: 0345 608 8551
Welsh Language: 0345 600 3018
Find out about call charges


Man United's attacking trio gives Solskjaer reason for optimism
by ReutersLONDON: Manchester United manager Ole Gunnar Solskjaer praised forwards Anthony Martial, Marcus Rashford and Mason Greenwood after their ruthless display in front of goal secured passage to the Europa League knockout stages with a 3-0 win over Partizan Belgrade.
Teenager Greenwood opened the scoring on Thursday before a spectacular solo effort from Martial in the 33rd minute, the first time United have scored twice in the first half at Old Trafford this season.
Rashford’s powerful strike four minutes into the second half put the result beyond doubt. “I’m very pleased with all of those finishes, all three goals were high class,” Solskjaer said.
“Mason showed great composure, … Anthony’s was probably the skill of the night, and then I was very pleased Marcus scored with his left foot. He’ll need more goals on his left because he is in that position often and he can go both ways.
“This is a little bit of a template of how we want to play. Of course, it’s the opposition that allow you to play that way as well.”
The only negative for Solskjaer on the night was an ankle injury to midfielder Scott McTominay in the closing stages of the match.
The 22-year-old has started all 11 of United’s Premier League matches this season but may miss Sunday’s game against Brighton & Hove Albion on Sunday. “It didn’t look too good,” Solskjaer added.
“He went over on the inside of his ankle. He said he was going to be OK out on the pitch because he is tough but then he had to come off. I hope he will recover for Sunday, but I am not sure.”


We had an affair with modernity. It came into the room wearing its underwear. It started dancing. We became aroused, enchanted by modernity’s illuminated body. We wanted the enchantment to last a little longer. But the magic of it wore off.
Lost Generation
Issue 3 / September 2015 / 11 Articles
Read Online
Get the Paperback
It seems strange then to associate artificial light with the light of the stars. Each is measured by a completely different time-scale. The life of a star is counted in aeons. It fills up time like an ocean flooding an island. The timescale of electric light on the other hand is defined by shock.
Rough Spirits
Issue 3 / September 2015 / 11 Articles
Read Online
Get the Paperback
the room in which I sleep
contains a freezer
bought in the 90s to guard
against the impending
collapse of the economy;
in it are said to be
berries from the dacha
unknown quantities of meat
fish caught by the son
and other survival necessities
Indefinite Leave to Remain
Issue 3 / September 2015 / 11 Articles
Read Online
Get the Paperback
It seems strange then to associate artificial light with the light of the stars. Each is measured by a completely different time-scale. The life of a star is counted in aeons. It fills up time like an ocean flooding an island.
Rough Spirits
Issue 3 / September 2015 / 11 Articles
Read Online
Get the Paperback
I guess in the end, we dust to pass the time. I could talk about this forever. Is there any need to finish anything at all? Perfection is our plight. And our saviour. Even if they do get one façade clean, ridiculous really, look at the size of the thing, it’s already time to go back to the one before!
Rough Spirits
Issue 3 / September 2015 / 11 Articles
Read Online
Get the Paperback


Arrests after police stop suspected drug deal taking place in West Bridgford
Five men were arrested
by Gemma ToulsonFive men were arrested in West Bridgford after police stopped a suspected drug deal.
Officers spotted two parked cars in Holme Road at around 7.30pm on Sunday, December 8.
After smelling cannabis, they investigated the scene.
The five men, aged 23, 23, 36, 40 and 45, were arrested after officers found a quantity of Class A and Class B drugs, including cocaine and cannabis, in the cars.
A spokesman for the force said all were arrested on suspicion of possession with intent to supply drugs, with one of the 23-year-old men arrested on suspicion of robbery, burglary and blackmail in connection with separate incidents.
The other 23-year-old man was arrested on suspicion of blackmail in connection with another incident.
The 36-year-old man was also arrested on suspicion of possession of a bladed article after officers recovered a knife at the scene.
Detective Inspector Kim Binns, of Nottinghamshire Police, said: “Our officers are committed to keeping our communities safe and last night’s arrests are an example of how, as a force, we endeavour to protect the public through proactive police work.”
To receive one WhatsApp message a day with the main headlines, as well as breaking news alerts, text NEWS to 07790 586202. Then add the number to your phone contacts book as 'Nottingham Post'. Your phone number won't be shared with other members of the group.


downloaded from github.com/aanand/feepogram
Methods
Attributes
| [R] | bloops | |
| [R] | length |
Class Public methods
new(bloops, &block)
Link
Source: show
# File lib/ext/bloops/songs/feepogram.rb, line 5 def initialize(bloops, &block) @bloops = bloops @length = 0 @sounds = {} @tracks = {} @track_lengths = {} instance_eval(&block) end
Instance Public methods
dub(sound_name, notes)
Link
Source: show
# File lib/ext/bloops/songs/feepogram.rb, line 49 def dub sound_name, notes catchup = @length - @track_lengths[sound_name] @tracks[sound_name] << ("4 " * catchup) @tracks[sound_name] << notes @track_lengths[sound_name] = length+32 end
metaclass()
Link
Source: show
# File lib/ext/bloops/songs/feepogram.rb, line 16 def metaclass class << self; self; end end
metaclass_eval(&block)
Link
Source: show
# File lib/ext/bloops/songs/feepogram.rb, line 20 def metaclass_eval(&block) metaclass.class_eval(&block) end
phrase(&block)
Link
Source: show
# File lib/ext/bloops/songs/feepogram.rb, line 44 def phrase(&block) instance_eval(&block) @length += 32 end
play()
Link
Source: show
# File lib/ext/bloops/songs/feepogram.rb, line 57 def play @tracks.each do |sound_name, notes| bloops.tune @sounds[sound_name], notes #puts "#{sound_name}: #{notes.gsub(/\s+/, ' ')}" end bloops.play sleep 1 while !bloops.stopped? end
sound(name, base, &block)
Link
Source: show
# File lib/ext/bloops/songs/feepogram.rb, line 24 def sound(name, base, &block) name = name.to_sym sound = bloops.sound(base) @sounds[name] = sound @tracks[name] = "" @track_lengths[name] = 0 block.call(sound) instance_variable_set("@#{name}", sound) metaclass_eval do define_method(name) do |notes| dub(name, notes) end end end


I have worked as an artist in 3D and VFX for the last 6 years working on such productions as Spartacus War of the Damned and the Wellington produced show Thunderbirds Are GO!
Have a huge interest in all things Digital and Film from Projection mapping, working and managing a team on set, designing and creating apps, architectural rendering, vr and game design.
I'm am now delving into to the world of web and software development
Feel Free to check out my blog and join me on this journey.


Previous: DESCRIPTION
The brackets indicate something which is optional. The brackets themselves are not actually typed. Here options are command-line switches or settings, which control the operation of the program and the amount of information that will be printed out. If no option is specified, the default action is to print error messages, warnings, and informational messages, but not the program listing or symbol tables.
Each option begins with the '-' character. (On VAX/VMS or MS-DOS systems you may use either '/' or '-'.) For the sake of conformity with an increasingly common convention, options can also begin with '--'. The options are described at greater length in the next section.
ftnchek options fall into two categories: switches, which are either true or false, and settings, which have a numeric or string value. The name of a switch is prefixed by 'no' or 'no-' to turn it off: e.g. -nopure would turn off the warnings about impure functions. The 'no' prefix can also be used with numeric settings, having the effect of turning off the corresponding warnings. Settings that control lists of warnings have a special syntax discussed below. Only the first 3 characters of an option name (not counting the '-') need be provided. A colon may be used in place of an equals sign for numeric or string setting assignments; however, we show only the equals sign form below.
The switches and settings which ftnchek currently recognizes are listed below. For each option, the default is the value used if the option is not explicitly specified, while the turn-on is the value used if the option is given without assigning it a value.
If the -mkhtml option is invoked and tree is the applied calltree option, a file named CallTree.html, will be produced depicting the tree in HTML format.
When more than one option is used, they should be separated by a blank space, except on systems such as VMS where options begin with slash ( / ). No blank spaces may be placed around the equals sign ( = ) in a setting. ftnchek "?" will produce a command summary listing all options and settings.
For settings that take a list of keywords, namely -arguments, -array, -calltree, -common, -crossref, -f77, -f90, -f95, -intrinsic, -makedcls, -mkhtml, -portability, -pretty, -project, -source, -style, -truncation, and -usage, the list consists of keywords separated by commas or colons. If the list of keywords is omitted, the effect is to set the option to its turn-on value (same as ``all'' in most cases). Also, if the list is omitted, the setting name can be prefixed with no or no- to turn off all the options it controls. For example, -f77 turns on all warnings about nonstandard constructions, while -nof77 turns them all off. Three special keywords are:
These three special keywords must be given in full. For all other keywords, only as many letters of the keyword as are necessary to identify it unambiguously need be given, or a wildcard pattern may be used. Including a keyword in the list turns the corresponding option on. For example, -f77=intrinsic would turn on only the warnings about use of nonstandard intrinsic functions. Prefixing a keyword by no- turns its option off. For example, -pretty=no-long-line turns off warnings about lines exceeding 72 columns in length while leaving all other warnings about misleading appearance in effect. If a setting has default none, you can turn on all options except one or two by using all first. For example, -f77=all,no-include enables warnings about all nonstandard extensions except INCLUDE statements. If a setting has default all, you can turn off all warnings except one or two by using none first. For example, -truncation=none,demotion would turn off all precision related warnings except about demotions. Wildcard patterns contain an asterisk to stand for any string of characters. If a wildcard pattern is used, all the warnings that match it are affected.  The minimum unambiguous length rule does not apply to wildcard matching. For example, use -usage=no-*var* to turn off all warnings relating to variable usage (both local and common). (Unix users may need to quote any options containing wildcards in order to prevent the shell from attempting to expand them.) Wildcards are recognized only in lists of warning keywords, not in the top-level options themselves.
When ftnchek starts up, it looks for environment variables and also for a preferences file. Any options defined in the environment or in the preferences file are used as defaults in place of the built-in defaults. They are over-ridden by any command line options. See the section on changing the defaults for details about the environment options and the preferences file.
When giving a name of an input file, the extension is optional. If no extension is given, ftnchek will first look for a project file with extension .prj, and will use that if it exists. If not, then ftnchek will look for a Fortran source file with the extension .for for VMS systems, .f for UNIX systems. More than one file name can be given to ftnchek, and it will process the modules in all files as if they were in a single file.
Wildcards are allowed in the specification of filenames on the command line for the VMS and MS-DOS versions, as also of course under UNIX and any other system that performs wildcard expansion in the command processor.
If no filename is given, ftnchek will read input from the standard input.
Next: OPTIONS


Here is the method that I use to update the UI when a background async thread. This is mostly for my own reference:
Continue reading
In one of my recent projects, the need to encode QR codes on the device came up. I tried a few different methods and wasn’t really satisfied with any of them.
The method detailed here is the one I chose based on ease of use and the quick set up time.
The core library is written in c and the base version can be found here: http://fukuchi.org/works/qrencode/index.html.en (download the entire project below).
Continue reading
One of the pieces of code I find myself re-using constantly is creating a gradient background for a UIView in iOS. This example will show two examples of how to create a simple gradient background.
Continue reading
D*Lite is an incremental heuristic search algorithm that is used by agents (game ai, or robots) where the surrounding terrain is not completely known. The algorithm makes assumptions about the unknown terrain. D*Lite finds the shortest route from the start to the goal position, and as it encounters new obstacles these are taken into account and only part of the path is modified. Alternatively, pathfinding algorithms like A* typically have to replan the entire path when the environment changes.
Continue reading


Verified Clans
The current list of officially affiliated clans in 1CC.
Here you can find the direct links to the clan Discords (Click on their logo or name). You can find a more detailed information panel about these clans in the #verified-clans channel of 1CC.
Closed and private clans will have an invitation link to a placeholder server or the 1CC server.
Remember that the orders of these clans on the list have no correlation to the skill of the clan. Choose any one you like!
_


expert help for custom Written
On the other hand, we denounce with righteous indignation and dislike men who are so beguiled and demoralized
On the other hand, we denounce with righteous indignation and dislike men who are so beguiled and demoralized


Clay figurine will be placed in different toy stores or certified LEGO store in a shopping mall and this game will require one electronic device, tablet or smartphone. The mechanisms are listed as below:
Log on to www.PowerUpHunt.com to check where Clay is located
Follow the the map, scan the shield design by using the Nexo Knights game.
This application is downloadable for Apple or Android devices, tablet or smartphone
Purchase minimum one minifigure or bricks set of Nexo Knights series. Fill in the lucky draw voucher, attach together with valid receipt and put them inside lucky draw box. Feel free to purchase the LEGO at any stores
Get two free lucky draw vouchers for every purchase of Jestro minifigure.
The more LEGO Nexo Knights are purchased the bigger chance to win the grand prize.
Winners will be announced on ( www.PowerUpHunt.com ), everyone is invited.


Do not try to authorize these pins with your account. If you want to test authorization, then clone this project and do it locally as anyone who vists this page can see your authorization token.
PIN: {{ pin }}
Request Id: {{ requestId }}
Expires In/Expired: {{ fromNow expireTime }}
Authorization Token: {{ authToken }}
Expired: {{ expired }}
authorized: {{ authorized }}
{{ /with }}


|
|
Power Saver. Printer will wake up when user sends a print job or by pressing the Power Saver button.
|
|
|
|
| Name: | WorkCentre 6605DN-2E7F8 |
| DNS: | Unknown |
| IPv4: | %LOCALIP% |
| IPv6(Link-Local Address): | %IPV6ADDRESS% |
| Fax Number: |<PHONE_NUMBER> |
| Contact: | |
| Location: | |
| Status: | Ready |
|
| |
Refresh Status |


|
Good day, You have just initiated a request to reset the password in Nimera account. To set a new password, please click the link below. |
|
| SET A NEW PASSWORD | |
|
For security reasons this link will expire in 24 hours. If you are not the one who has made it, please contact us immediately via support link below: |
|
| WRITE TO SUPPORT | |
|
If this activity is not your own operation, you can disable your account via this link. |
|
| DISABLE | |
|
Please note that clicking/tapping this button leads to account freeze and KYC verification level reset. Restoring access to account implies contacting Nimera support team, and re-progressing through KYC verification steps. |


Simple DB Tool
Query
Configure
About
x
Save a Profile
Name
Something like "My Company Creds" or "Personal Account"
AWS Access Key ID
AWS Access Key ID
AWS Secret Access Key
AWS Secret Access Key
Profiles
Name
Access Key ID
Edit
Use
Delete
No profiles...
Create a new profile


2 Corinthians 8:11
Now therefore perform the doing of it; that as there was a readiness to will, so there may be a performance also out of that which ye have.


JSON-stat from an API
Click the axis and legend titles to demonstrate axis changes.
CSV from static file
Click the axis and legend titles to demonstrate axis changes.


This intention converts two nested if statements into one if statement containing conjuction operation in it.


//
Designing A Professional Website
I've needed a portfolio website for a LONG time. The goal with this one was to make it mobile friendly, cross-platform, and intuitive. All of the code is custom and I didn't use
a template or anything like that. All of the designs are my own. If you want to know more, just look around! There is a lot to see. The home page display boxes took a good bit
of time. They are dynamically placed when the page loads. This will allow me to add more in the future. I had to create an algorithm to place them all without any blank space
in a way that looks good. Again, I feel the website speaks for itself about the extent of my web design skills. Show, not tell, as they always say!
Copyright © 2016 Daniel Timko


Board posts deleted notifications ('0' — disabled, '1' — enabled).
Board posts edited notifications ('0' — disabled, '1' — enabled).
New board posts notifications ('0' — disabled, '1' — enabled).
Board posts restored notifications ('0' — disabled, '1' — enabled).
Sets whether Long Poll is enabled ('0' — disabled, '1' — enabled).
Community ID.
Joined community notifications ('0' — disabled, '1' — enabled).
Left community notifications ('0' — disabled, '1' — enabled).
A market comment has been deleted ('0' — disabled, '1' — enabled).
A market comment has been edited ('0' — disabled, '1' — enabled).
New comment to market item notifications ('0' — disabled, '1' — enabled).
A market comment has been restored ('0' — disabled, '1' — enabled).
Allowed messages notifications ('0' — disabled, '1' — enabled).
Denied messages notifications ('0' — disabled, '1' — enabled).
A message has been edited ('0' — disabled, '1' — enabled).
A new incoming message has been received ('0' — disabled, '1' — enabled).
A new outcoming message has been received ('0' — disabled, '1' — enabled).
A photo comment has been deleted ('0' — disabled, '1' — enabled).
A photo comment has been edited ('0' — disabled, '1' — enabled).
New comment to photo notifications ('0' — disabled, '1' — enabled).
A photo comment has been restored ('0' — disabled, '1' — enabled).
New photos notifications ('0' — disabled, '1' — enabled).
A vote in a public poll has been added ('0' — disabled, '1' — enabled).
User added to community blacklist
User removed from community blacklist
A video comment has been deleted ('0' — disabled, '1' — enabled).
A video comment has been edited ('0' — disabled, '1' — enabled).
New comment to video notifications ('0' — disabled, '1' — enabled).
A video comment has been restored ('0' — disabled, '1' — enabled).
New videos notifications ('0' — disabled, '1' — enabled).
New wall posts notifications ('0' — disabled, '1' — enabled).
A wall comment has been deleted ('0' — disabled, '1' — enabled).
Wall replies edited notifications ('0' — disabled, '1' — enabled).
New wall replies notifications ('0' — disabled, '1' — enabled).
A wall comment has been restored ('0' — disabled, '1' — enabled).
New wall posts notifications ('0' — disabled, '1' — enabled).
Generated using TypeDoc
New audios notifications ('0' — disabled, '1' — enabled).