text:
This allows "git checkout -d v1.4.3" to detach the HEAD from any branch but point directly at the named commit. After this, "git branch" starts reporting that you are not on any branch. You can merge into "current branch" although there is not even such a thing. You can go back the normal state by switching to an existing branch, say, "git checkout master" for example. Another way to get out of this is "git checkout -b newbranch". This is still experimental. While I think it makes sense to allow commits on top of detached HEAD, it is rather dangerous unless you are careful and know what you are doing. Next "git checkout master" will obviously lose what you have done, so we might want to require "git checkout -f" out of a detached HEAD if we find that the HEAD commit is not an ancestor of any other branches. On the other hand, the reason the user did not start the ad-hoc work on a new branch with "git checkout -b" was probably because the work was of a throw-away nature, so the convenience of not having that safety valve might be even better. We'll see. Signed-off-by: Junio C Hamano <firstname.lastname@example.com> --- builtin-branch.c | 36 ++++++++++++++++++++++++++---------- cache.h | 2 +- git-checkout.sh | 22 +++++++++++++++++++--- path.c | 26 ++++++++++++++++++-------- setup.c | 5 +++-- 5 files changed, 67 insertions(+), 24 deletions(-) diff --git a/builtin-branch.c b/builtin-branch.c index 745ee04..71f88f2 100644 --- a/builtin-branch.c +++ b/builtin-branch.c @@ -299,7 +299,8 @@ static void print_ref_list(int kinds, int verbose, int abbrev) free_ref_list(&ref_list); } -static void create_branch(const char *name, const char *start, +static void create_branch(const char *name, const char *start_name, + unsigned char *start_sha1, int force, int reflog) { struct ref_lock *lock; @@ -318,9 +319,14 @@ static void create_branch(const char *name, const char *start, die("Cannot force update the current ...
[Note: casual git-user speaking] This is fine. Often you want to test a couple of tags, one after another, so "git checkout v1", "git checkout v2", ... Wth should this do? I already noticed this line in your posting from 29.Dec: [slightly edited] $ git checkout v1.5.0 Checking out a tag -- you are not on any branch now... $ <modify> $ git commit -m 'fix' -a You cannot commit without a current branch. $ git checkout -b maint-1.5.0 $ git commit -m 'fix' -a I assume it will create a new branch and modify HEAD so that the current working dir/index gets committed into that branch. (Basically "git branch main-1.5.0 && echo 'ref: refs/head/main-1.5.0' >.git/HEAD") If that's the case, I was looking for that incantation for a long time and couldn't find it. I'm using the git-branch and echo as shown above to get that. The man-page isn't very helpful for that special case of git-checkout. Anyway, if I want to commit and git tells me that I can't because I'm not on a branch, the _most unintuitive_ thing would be calling 'git-checkout'. I want to checkin! No way that I call checkout and risk losing all my changes. What's wrong with a -b option to commit, similar to -b on checkout? $ git checkout v1.5.0 Checking out a tag -- you are not on any branch now... $ <modify> $ git commit -m 'fix' -a You cannot commit without a current branch. Give '-b <newbranch>' to commit into a new branch. $ git commit -b maint-1.5.0 -m 'fix' -a Another variant (the one I prefer): commit just updates HEAD and git-branch can be used to give it a name (and switch to it!). So these workflows would be possible: Name after commit: $ git checkout v1.5.0 Checking out a tag -- you are not on any branch now... $ git branch master * (unnamed) c8ff51290518949225c832bae1e22b1bba6ab2cd $ <modify> $ git commit -m 'fix' -a Warning: data committed into unnamed branch. Give it a name now with "git branch <newname>" $ git branch master * ...
Being able to perform "checkout" with a tag like this, (and no specific branch), is something I've been wanting git to acquire for This part I don't understand. I don't see why it's useful to introduce new danger to "git checkout" in that after this change it could cause commits to become dangling. Currently, "git checkout" is entirely safe, as are most git commands. The few commands that create dangling commits require fairly explicit actions from the user, (such as "--hard" for git-reset or -D instead of -d for git-branch). So I'd vote against this aspect. I'd rather see commits to a detached head be disallowed with a message instructing the user to do "git checkout -b new-branch" in order to do the commit. And with that new safer behavior, I think it would be a good idea to just drop the "-d" option from git-checkout. I want this new behavior not for people who know what they are doing, but people who are using git only incidentally, (say they just want to acquire and build the latest version of some software). So I'd like the sequence to work along the lines of your earlier post, (as quoted by another reply). Specifically, I wouldn't want to see any warning about a "missing branch" until a commit was attempted. This would allow a sequence like this to proceed without git ever telling the user they were doing something "wrong": $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git $ git checkout v1.4.3 $ make With the recent improvements to the git-checkout error message (thanks!) this sequence is at least successful eventually after the user reads and responds to the following: git checkout: provided reference cannot be checked out directly You need -b to associate a new branch with the wanted checkout. Example: git checkout -b <new_branch_name> v1.4.3 But the user is required to invent a name and deal with its existence later. For example, after some time, imagine the same user wanting to update to the latest and build ...
I am not saying being risky is useful. That's why I said it is experimental. We could do two things, and I think disallowing commits is not necessarily a better option of the two. We could allow commits and prevent the user from switching out of the detached HEAD state without an explicit action instead. If we go the first route, you need to also prevent merges into the detached HEAD. If we go the latter I think you only need to add a check in "git-checkout" but there may be other cases. In either way, we need a safety valve, which the experimental code does not have. And being able to merge into the detached HEAD turns out to be somewhat useful. I checked out the v188.8.131.52 and tried to see if a topic is applicable by merging into that detached HEAD and running testsuite. Of course, without any safety valve, I can easily lose the merge result by switching out of the detached HEAD state (say, "git checkout master"), but on the other hand, creating a new branch at that point with "git checkout -b v184.108.40.206-maint" would let me continue from that point without losing anything. But this is only "somewhat" -- I do not have strong opinion either way, other than that we need a safety valve (which we agree). In any case, I did this because I got tired of waiting for it to happen (I thought you wanted to hack on this over the long week^W yearend, so I deliberately stayed away from doing this) and I was bored. This will not be in 'next' in the current shape. You've thought about the issue long enough to write your commentary and I agree to most of your points (including favoring "no commit allowed in this state" over "allow commits and merges to help advanced usage" for its simplicity), so if you code it up with a clean patch, I would not reject it on the basis of its design. -
Yeah, that would be fine too. Personally, I'd be happy with either OK. I guess I misinterpreted things. I was afraid that you were proposing a safety valve on _entering_ the detached state, (perhaps the -d option to checkout itself). It was the requirement of something extra to checkout a tag (as opposed to checkout of a branch) that I I'm glad you went ahead. I ended up almost not touching computers at I don't actually prefer "no commit allowed". I just didn't want the user to have to explicitly disable the safety before being able to perform a checkout based on a tag. I am still interested in this feature, so I will try to find time to come back with a revised version of your patch with the missing safety check (and without requiring -d on checkout). Thanks again for this initial take on the problem. (Though if anyone else beats me to it, I certainly will not be offended.) -Carl [*] I did play some nice new (to me) board games, (Zendo and DVONN being standouts), but thats a topic for elsewhere I suppose.
Ok, then I think we are in agreement that the safety should be Sounds good. I do not mind losing -d, but I would suggest that there should be a message that says "you are no longer on any branch" after a checkout that makes the head detached. The user should be warned about such an unusal situation. -
I decided to fast-track this one. With a handful fix-ups, this is now at the tip of 'next'. The primary difference from the one we discussed, and then has been sitting in 'pu', is that coming back from the detached HEAD state is allowed only with '-f' or to a branch that is a fast-forward of HEAD. So you can do: git checkout v1.2.0 ;# detach ... look around ... git checkout v1.4.0 ;# still detached ... look around ... git checkout master ;# Ok, because v1.4.0 is an ancestor of master but you would be warned and asked to say -f if you do: git checkout v1.4.0 ;# detach edit ... git commit -a -m 'some tweak' git checkout master ;# Not Ok -- you may lose that commit. An alternative exit in this case is to create a new branch at that point. So this does work: git checkout v1.4.0 ;# detach edit ... git commit -a -m 'some tweak' git checkout -b maint-1.4.0 ;# start the maint-1.4.0 branch Have fun. -
I haven't seen the code, waiting for kernel.org to mirror, but I have a Hrm. So does that mean this doesn't work (without -f): git checkout v1.4.0 ... look around ... git checkout v1.2.0 I think a better (but more expensive) check would be "coming back from the detached HEAD is allowed only with '-f' or if HEAD is an ancestor of any non-HEAD ref." -Peff -
That should work. The first checkout, because there is no branch v1.4.0, makes the HEAD detached. You are no longer on any branch at that point, and "git checkout v1.2.0" that follows do not trigger the check which is about "coming back from the detached HEAD state". But I would probably do the second v1.2.0 "checkout" with "git reset --hard", if what I am doing is "wandering, looking around to see different commits". -
So what's the final check? Is it "can come from detached HEAD to a branch only if the detached HEAD is reachable from the target branch"? If so, that's still a trap for people who are just exploring with "git You would probably do this, yes, but is it what you would recommend in a tutorial for new users doing read-only exploration of old versions of some piece of software? One of the main reasons I'm interested in the "detached head" stuff is so that such users can use "git checkout" to explore any revision and never have to worry about doing anything "wrong", (never leave any commits dangling), nor ever have to see any "scary" message, (ie. "use checkout -f if you know what you are doing"). -Carl PS. Thanks for giving detached head some attention---I'm chronically inept at getting into actual git development like I'd really like to.
An obvious alternative is not to allow building on top of a HEAD that is detached at all, which I suggested initially. A non-alternative is to silently lose commits, which you seem to be suggesting, but I would rather play it safe. The wording used for current warning that says "use checkout -f" is horrible, and it needs to be reworded much better, but other than that, I think playing safer is much better than making a worse trap of silently losing the commits they may make before they come to understand how "a branch" works. -
That sounds great to me. Let's just suggest "checkout -b" before commit, (maybe even add new "merge -b <newbranch>" and "commit -b <newbranch>" so the suggest command could be even closer to what the No, I would never want that. We both agreed earlier that a safety valve is necessary. I just want to make sure that people that never actually need it don't have to see the message. And I don't think that _that_ part would be feasible with the safety valve at the point of "leaving detached state". It would basically come down to having to do reachability analysis for the current HEAD from all known branches or something equally horrific. So let's put the safety valve where it's cheap to detect and where we know it will distinguish between read-only and read-write use, (that is, put it precisely at the point where there's an attempt to create a new commit object while in the detached state). -Carl
The common case is probably going to be where the argument to `git checkout` is a fast-foward of the detached HEAD. And that's pretty cheap to check. So we perform that check, and if we fail that then we search through every ref to determine if the detached HEAD is fully contained in any of those. Currently that would be pretty slow to do with the current tools, but a small modification of say git-merge-base (or git-describe) might make it cheap enough to run during this slightly less common case. No need to complicate merge/am/rebase/revert/commit/applymbox with a -b option. -- Shawn. -
The needed change to merge-base is quite minimum. Let me come up with a patch... -
Yes, I agree. From my point of view, the question is where does it "go" committing changes on top of a "detached HEAD". Commits shold probably be only allowed on top of local branches, since creating the branch itself shows an intention, possibly intention to do work, to commit new things. Luben -
Oh, that's even worse, since the safety valve doesn't kick in when it should. For example, with what's in next now, I can do this: git checkout v1.4.0 hack hack hack git commit -m -a 'some changes which will never be seen again' git checkout v1.2.0 As Carl mentioned, I think recommending that workflow is a terrible idea from a user interface perspective. -Peff -
Fair enough. We could always do the check upon "git checkout" from a detached HEAD state, whether it takes you back on some existing branch or leaves your HEAD still detached. -
Stupid question: why can't checkout do something like this? if we're currently not on a branch, fail if .git/PREV doesn't point to the same commit as .git/HEAD. if we're checking out a non-branch, store its SHA1 into .git/PREV. So the user gets a warning (overrideable with some kind of --force option) if they do a checkout when the HEAD isn't exactly what they last checked out. Then git checkout master git checkout v1.4.0 git checkout v1.2.0 git checkout master all works without complaints, but the example above gives a warning at the "git checkout v1.2.0" point. --b. -
I would guess the problem is that this would still cause warnings even if the user had since given a name (created a branch) for the commits originally made to the dangling head. Frankly, I don't understand why so much effort is being put toward allowing these "fragile commits" to be made in the first place. Why not require users to name the branch before creating any commits, just as has always been the case? To me, the only real advantage to the new "detached head" stuff is simply making it easier to checkout previous state without having to name a new branch precisely _because_ the user has not intent to commit anything. If the user is going to commit something, then the user should be able to come up with a name for the branch. But, whatever, if allowing fragile commits is seen as important by those doing the work, who am I to complain about that? I'd just ask that the following not be made slow: git checkout commit-from-beginning-of-time git checkout master Thanks to the index, and the simplicity of what "git checkout" means, checkout has always been blisteringly fast. All the talk of doing reachability analysis scares me from a performance point of view, (particularly when the _interesting_ cases (to me) of checkouts to non-branches never need this anyway---since no commits will be made). Thanks, -Carl
I think as long as we provided a special exception for a case like "git checkout -b": git checkout v1.4.0 hack hack hack git commit -m -a 'some changes' git checkout -b new-changes and also provide a way out (--force-checkout-losing-current-head) for people that really know what they're doing, that should be more than enough to handle that sort of case. Because, I agree, the point is to make easy what 90% of users will probably do, at least on the first encounter with git--download project X, checkout version Y, build--and making checkouts on detached commits convenient seems a lower priority. --b. -
The safety valve I was proposing would be only the additional time of running `git merge-base commit-from-begging-of-time master` to verify the former is completely contained in the latter. That's going to be true, and is a relatively fast operation (roughly linear in time with the length of the history). However in this case: git checkout v1.5.0 git checkout v1.2.0 would take slightly longer as we'd have to verify that the HEAD from the first checkout is contained in an existing tag/ref. Which it is. Since its probably exactly equal to one of those dereferenced tags this may just wind up being the cost of scanning the .git/packed-refs file. You do pack your refs, don't you? In my mind that is a small price to pay for making sure the commit currently in a detached HEAD doesn't get orphaned off into never-never land. -- Shawn. -
Agreed. Possibly, we could have commit (or commit-tree) issue a big fat warning along the lines of: *** WARNING *** You are about to create a commit on a detached HEAD. It is recommended that you run "git branch <name>" to create a branch to commit to first. If you don't, you might lose this commit further on. *** WARNING *** which could be suppressed by a "--silently-ignore-detached-head" in case scripts (securely) use this behaviour. Since committing on detached heads really should be a very rare case I don't think many people will Indeed and as I've said before, *all* developers have "silly-names" they use for temporary stuff (foo, bar, frotz, nitfol, blaj, fnurg, sdf, ...) so it's not like we'll put a heavy burden on peoples imagination. -- Andreas Ericsson firstname.lastname@example.com OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 -
Quite the contrary, I would imagine it would be quite natural to do throw-away commits and merges on detached head while bisecting the history (e.g. commit small fixup to make it compile and then mark the result for bisection to hunt for real bugs that are hidden by silly compilation problems). The check suggested by Linus would be safe enough for people to whom it is "very rare" for their workflow to commitg on detached HEAD anyway, so you should not burden "git commit" with such an annoying warning messages. -
I don't think this would actually work. If you commit your build fix, and then mark the result as bad, won't bisect skew its choices due to suspecting that your build fix is the real bug? I'd think that, if you make changes while bisecting, you probably want to leave those changes uncommitted, and merge or discard them when testing other commits. If anything, I'd think you'd want a rather different sort of commit mechanism than the usual commit, which says, "whenever you consider commit {sha1-from-real-history}, use {tree-with-local-changes} instead of {tree-in-real-commit}." Or, more generally, "in order to get the trees I want to actually use, this patch (git diff HEAD) needs to be applied to every commit in some portion of the history including, at least, get_sha1(HEAD)". I'm not seeing any actual benefit to causing the history to contain a dead-end fork off of an antique commit, and then throwing this away. And committing your change so that it won't get lost, with the intention of losing it in a little while, doesn't seem to make any sense, either. (Of course, it also makes sense to do merges, but again, you probably want to create and temporarily use the working tree resulting from the merge, not create the commit.) I think that the workflow that uses regular commits with a detached HEAD is this: do a series of commits representing real work on top of a remote branch or a tag, and decide later (once you've tested the results for worthiness) whether to turn this into a topic branch or throw it away. But I don't think this is a good match for detached HEAD, because you may want to do exactly the same thing, but start with a regular local head. I think the right thing to do is something like "git checkout --anon", which puts you on a new branch with no name, which will evaporate if you leave it (as per "git branch -d"; you need to force it if it isn't fully merged). So I think the feature which lets you make commits without being on a ...
Same here. I'd imagine temporary build-fixes to live as a patch-file generated by git diff > build-fixes.diff after having hacked on the tree. There's no sane way of inserting commits into the middle of the DAG, so committing on something that Yes. I'd imagine "git merge --no-commit" could be used for this, to Perhaps, but this is also a bit weird, as you would normally hack things up to fit on top of some already existing branch, so then you'd detach the head but point it to something that already has a branch-name associated with it. Otoh, I could imagine this would be sort of nifty for applying bugfixes on top of old tags, so perhaps it's not so weird after all. Then you'd probably want to create a new tag before releasing the bugfixed version, so Linus suggestion makes sense in this case (assuming it doesn't fsck Yes. I'd imagine "git merge --no-commit" could be used for this, to merge things only in the working directory. We could easily create a hack for this by doing a "git reset --mixed HEAD^1" after the merge is Agreed. They really are two completely different things. I see no harm in splitting them up codewise. Bisect could start working without its protected branch straight away, but commits (and merges) to detached heads wouldn't work at all. Then we can see what use people put this to and what walls they run into and make the feature accordingly. -- Andreas Ericsson firstname.lastname@example.com OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 -
Then we would not be talking about detached HEAD at all. Why not require users to name the branch if they want to check out what they should not be able to in the first place? Convenience. Some features of git are about being convenient by allowing you to defer the decision. You can start mucking with the working tree files without knowing where it leads to and then from that point with the dirty working tree state decide to fork what you have started using "checkout -b newbranch". Even though you may have many dirty files in the working tree, you can selectively update index (especially with the patch subcommand of the interactive git-add) to prepare for commit -- you do not choose what to edit, but you defer the decision of what to include in the commit. -
I do not want to think about the consequences of adding more cruft under .git/ directory. For example, should PREV be noticed by fsck and prune? What should various forms of 'git-reset' do with it? How does it interact with 'git-bisect'? Being able to test merge or even make commits without being on a branch is vastly useful. It might or might not lead to anywhere even after you make a handful commits -- and I would imagine that it would be very handy to be able to be lazy and not having to decide if it is worth a new branch. But that may be just my imagination; I generally prefer any feature that allows me to defer decision over something that makes me decide early. If Carl wants to do a patch to teach 'git-commit' (and all other things that can create commits) not to do things from working in a detached HEAD, I would probably not opposed to it too much, but I am fairly certain that I won't be coding it myself. It's tempting to forget about this whole "safety" business. Because we allow "reset --hard" and other forms of operations that can lose history if they were done while on a branch, only giving the safety to "git checkout" feels somewhat silly. And the primary motive for detached HEAD as I understand it is for sightseeing, and not allowing "reset --hard" to jump around is just plain silly. That is, after: git checkout v1.4.0 you are not on any branch, and we would still allow git reset --hard v1.2.0 which is exactly the same as: git checkout v1.2.0 You can still say: git checkout master and we do not even check. Which makes the "merge-base --check-ancestry" stuff I did last night pretty much unnecessary, but that's Ok. It will find other uses. -
I agree. The reachability list for those is already starting to get out of control, and the rules for making sure those files are always in sync with every command is getting crazy. Didn't we just fix `git reset --hard` to throw away .git/MERGE_MSG? That's been a longstanding bug right there, and that's something that has been I agree. I'm always creating and deleting `foof` because I need someplace to work real quick. Being able to work on a detached HEAD would just slightly streamline the process, especially given that `git checkout -b a-real-name` is readily available to move that My concern here is to hit all of the corner cases. reset. bisect. am. rebase. merge. cherry-pick/revert. Did I get all of 'em? But isn't the --hard switch the safety valve here? And lets not forget that reflogs are enabled by default now so even a `reset --hard` on a real branch isn't a total loss (its only a loss for uncommitted files in the working directory). But a detached HEAD has no reflog. Which means operations that update it in a non-fastforward way would orphan work. A subsequent gc/prune/repack might destroy it, unless an existing ref contains Pity. It looked like it was a good change and would be useful here as a safety valve. Though based on what you said above I would think we'd actually want it in both checkout and reset (--soft and --hard versions). -- Shawn. -
Yes. I think the detached head notion is really really important. I think it was a mistake to not allow it initially, but hey, there were various historical reasons, and the whole thing about how branches worked was a bit up in the air. I would suggest a solution: - git checkout will refuse to switch AWAY from a detached head unless the SHA1 of the detached head exactly matches some other branch. Not any expensive "reachability" cheaks. Simple and straightforward: just say "no, I will not leave this branch-less HEAD behind, because it is not described by any other branch or tag". So if you do git checkout v1.4.4 you'll be fine, because even though you got a detached HEAD that isn't attached to any branch, it still exists as a tag, so checking out something else is fine - you've not lost any state. In contrast, if you actually start committing to that detached HEAD, you need to either - use some new flag ("git checkout --forget-old") to explicitly say that you _want_ to leave this old naked branch behind - either tag the current point or make a real branch out of it (with either "git tag <tagname>" or "git branch <branchname>" respectively) and then you can check out some other tag/branch after that. Doing "reachability analysis" is not only expensive, it's actually really wrong, because even if the current HEAD is _reachable_ from some other tag or branch, you're still going to drop that point in the development series unless it _exactly_ matchs it. Hmm? I'd love to see the detached HEAD series move into "master", but I do think we should make sure that people can't drop their work easily by mistake, and I think the above suggestion is both simple and workable. Comments? Linus -
I agree with the "reachability is wrong -- you would lose the point in the middle" reasoning. -
I have no problem with that. Forget the reachability thing entirely. My point about reset --hard/--soft probably also needing this check still stands however. -- Shawn. -
Well, I disagree, if only because the whole _point_ of "git reset" is to leave some point behind. I use it all the time (well, often enough) as a "undo" operation, and it's fundamentally different than "git checkout" at least to my worldview. When you do "git reset" you _expect_ state to be reset/dropped. But when just switching between branches, you don't. (I realize that "git checkout filename/goes/here" has kind of mixed up "git reset" and "git checkout". The "git checkout filename" syntax basically resets the filename, and that confuses things a bit. So in the above, I really do talk about just "checking out a _commit_" and do a state switch, not a "check out a filename" and overwrite the old contents of that file). Linus -
That's a nice cheap check. But I've also been liking the idea of using this "detached head" stuff for git-bisect, (instead of making it carry around its own temporary branch). One long-standing user-interface bug with git-bisect is that often the user doesn't know a priori what the last-known-good state is to initially mark with "git bisect good". So I've long wanted a good clean way to explore fairly arbitrarily in order to get git-bisect jump started. When I first started using git a year ago, what was suggested to me for this, (and what I've used ever since), is: git checkout -b tmp some-guess-at-a-good-commit # check it git reset --hard next-guess-at-a-good-commit Obviously, that works but fails the "good clean" test for me. Half the time it fails for me and I have to "git branch -D tmp" first. Then there's the fact that I want very new users to learn git-bisect---I want random users that have hit bugs in my software to bisect those bugs for me---and many of these users will have never seen git before. I don't think it's kind to start their education with "git reset --hard". I'd like to instead teach them something as simple as: git checkout some-guess-at-a-good-commit # check it git checkout next-guess-at-a-good-commit I wouldn't want these uses to trigger warnings just because the user is checking out arbitrary revisions from the logs rather than using tags and branches. But, yes, as soon as the user actually _commits_ in the detached state, then a check for "HEAD == some branch" should be just fine for checking a checkout to somewhere else. -Carl
I've done this, also added one fix and merged the topic to "next". I am hoping I can move this to "master" by the weekend. -
If the detached HEAD matches another branch what did we need a detached HEAD for in the first place? Seems that this check will in practice always be true. A detached HEAD by definition doesn't match some other branch. Have I misunderstood? Perhaps you meant the detached HEAD is /on/ some other branch? Andy -- Dr Andy Parkins, M Eng (hons), MIEE firstname.lastname@example.com -
Tags. Previously you could not checkout a tag without first making a branch from it. Now you can. -- Shawn. -
You are forgetting this: git checkout v1.0.0 -
No I'm not. Linus's suggested check is "git checkout will refuse to switch AWAY from a detached head unless the SHA1 of the detached head exactly matches some other branch." My question is what use is that? In exactly the situation you describe HEAD doesn't match a branch. git checkout v1.0.0 HEAD after that doesn't match any branch so the next "git checkout" will find that HEAD doesn't match any branch and will refuse to switch away. Why? A checkout in this case isn't dangerous at all. Of course I could still be misunderstanding. If Linus meant "refuse to switch AWAY from a detached HEAD unless the hash of the detached head exactly matches some other ref", I would be less confused. Andy -- Dr Andy Parkins, M Eng (hons), MIEE email@example.com -
I believe that's what Linus meant. As otherwise you are right, it doesn't make much sense. :-) -- Shawn. -
You are taking it too literally. Read what Linus wrote again. So if you do git checkout v1.4.4 you'll be fine, because even though you got a detached HEAD that isn't attached to any branch, it still exists as a tag, so checking out something else is fine - you've not lost any state. The version in "next" does that, in a quite straightforward way: git show-ref -d -s | grep "$old" || { barf } which should be fairly fast in a repository with packed-pruned refs. -
What about git checkout HEAD~20 I agree that checking out tags will be more common, but it feels like we are discouraging this usage by presenting spurious warning messages. -Peff -
Once the user knows what HEAD~20 means, I think it is safe to assume that the user knows what the branches are. "git checkout master" will barf and suggests the user possible common exits; "checkout -f" if there is nothing of value, "checkout -b <branch>" or if they want to build on the current state. And once the user who knows what the branches are sees such, and especially with the help from $PS1 hack of bash-completion in contrib/ section, the user will learn to do "checkout -f" after wandering around for sightseeing on a detached HEAD, and at that point the annoying error message will not be even seen. -
I'm interested of course in making life easy for project admins when they need to tell testers how to get code to test out of git. It'll be nice to able to say: "Install git, then run git clone git://ourproject.com/ourproject.git cd ourproject git checkout <version you want> " Instead of having to say "Install git, then run git clone git://ourproject.com/ourproject.git cd ourproject git checkout -b FOO <version you want> Then if you later need to check out another version, run git reset --hard <other version> " I suppose <version you want> will typically be either some tagged release or the latest head. But it's not that farfetched to imagine That should make it easy enough, though, I guess. --b. -
I think you should only enact this safety valve if there have actually been commits. Otherwise, people who are just tracking and do a "git-checkout v1.4.0; look look look; git-checkout v1.5.0" will get a confusing message. Personally, I like the "don't allow commit without a branch" approach, but only if you can "git-commit -b newbranch" and "git-merge -b newbranch" to make it convenient to create a branch. Making commits that aren't on any branch seems like a broken state (and indeed, you have to use special options to get out of the state); it makes more sense to me to never enter the state in the first place. Also, the implementation should be conceptually simple. Put refs/tags/v1.4.0 into HEAD on checkout. Disallow commit/merge unless HEAD points to refs/heads/*. Just my 2 cents... -Peff -
Let me take that back. It is actually still annoying to implement, since many things (at least commit-tree, branch) are unhappy with a non-branch in HEAD. Moreover, it's not as flexible as simply putting the commit sha1 into the HEAD, as you suggested. My suggestion allows only non-branch refs to be checked-out; however, it's likely somebody might want to git-checkout HEAD~10 or some other unnamed thing. -Peff -
This makes git-branch show a detached HEAD as '* (no branch)'. Signed-off-by: Lars Hjemli <firstname.lastname@example.com> --- This might be a premature patch. But if/when we allow HEAD to be detached, git-branch should tell us that HEAD is the current 'branch'. builtin-branch.c | 103 +++++++++++++++++++++++++++++------------------------- 1 files changed, 55 insertions(+), 48 deletions(-) diff --git a/builtin-branch.c b/builtin-branch.c index 71f88f2..16f86cc 100644 --- a/builtin-branch.c +++ b/builtin-branch.c @@ -231,29 +231,54 @@ static int ref_cmp(const void *r1, const void *r2) return strcmp(c1->name, c2->name); } -static void print_ref_info(const unsigned char *sha1, int abbrev) +static void print_ref_item(struct ref_item *item, int maxwidth, int verbose, + int abbrev, int current) { + char c; + int color; struct commit *commit; char subject[256]; + switch (item->kind) { + case REF_LOCAL_BRANCH: + color = COLOR_BRANCH_LOCAL; + break; + case REF_REMOTE_BRANCH: + color = COLOR_BRANCH_REMOTE; + break; + default: + color = COLOR_BRANCH_PLAIN; + break; + } - commit = lookup_commit(sha1); - if (commit && !parse_commit(commit)) - pretty_print_commit(CMIT_FMT_ONELINE, commit, ~0, - subject, sizeof(subject), 0, - NULL, NULL, 0); - else - strcpy(subject, " **** invalid ref ****"); + c = ' '; + if (current) { + c = '*'; + color = COLOR_BRANCH_CURRENT; + } - printf(" %s %s\n", find_unique_abbrev(sha1, abbrev), subject); + if (verbose) { + commit = lookup_commit(item->sha1); + if (commit && !parse_commit(commit)) + pretty_print_commit(CMIT_FMT_ONELINE, commit, ~0, + subject, sizeof(subject), 0, + NULL, NULL, 0); + else + strcpy(subject, " **** invalid ref ****"); + printf("%c %s%-*s%s %s %s\n", c, branch_get_color(color), + maxwidth, item->name, + branch_get_color(COLOR_BRANCH_RESET), + find_unique_abbrev(item->sha1, abbrev), subject); + } else { + printf("%c ...
It would be nicer if when you are on a remote tracking branch or on a tag that the name of the tag or the remote tracking branch is shown rather than '* (no branch)'. -- Shawn. -
I fully agree with the motivation, but 100 lines of change to adjust only to detached HEAD seems too much. What else is going on in this patch, I wonder... Can we have two patches, one for loop restructuring without detached HEAD support, and then another to add support for it? -


text:
Stainless-Steel Breading Pan, Set of 3
Breading Pans, Set of 3
This set's three shallow pans link together to form an efficient workstation for breading foods with minimal drips and mess.
- Efficient assembly-line prep station for breading.
- Three shallow pans hold bread crumbs, beaten egg, nuts or flour.
- Pans link together to prevent dribbles and mess.
- Durable 18/10 stainless steel.
- Dishwasher safe.
- 8 1/2" x 6" x 1" high.
- Made in China.
- Dishwasher safe.
Shipping Information
This item is shipped from our warehouse by UPS to arrive within five business days of our receiving your order.
Shipping Rates
The shipping rate varies depending on your order total and shipping destination.View Shipping Options and Charges.
Rush Delivery
For an additional charge of $15 per address, we can rush delivery to most destinations. This service is not available for some oversize items, items shipped directly from the supplier (including perishable and custom-manufactured items), out-of-stock items and items to be shipped outside the contiguous 48 states.
Return Policy
At Williams-Sonoma, we take great pride in the quality and craftsmanship of our products. If, within 90 days, you are not completely satisfied with your purchase for any reason, please return the item for an exchange or refund of the merchandise value. View Full Return Policy.

subset: commoncrawl


text:
Excellent I'll put it into the car then.
Soup weather do you think ? I could pack the big pot too, get it on early and there'll be a bite to eat.
Is there anything any one particularly wants to make/focus on ?
I've got four stones bored out to make pump drills but I need to make spindles. It'd be good to have them finished ? make the assorted tips too ?


text:
Orange Billing Manager
Track spending. Paperless billing details at a glance.
manage your mobile phone and billing
your company's billing for all your employees
manage your devices and talk plans and purchase on line
Managing your account online is convenient and easy using Web Self Serve. It's a free service available to business customers with over 50 handsets.
It lets you:
With Web Self Serve you can access and manage your account in real-time, whenever you choose. It shows all the details of your devices and accessories. You can also use it to contact Orange with any questions you might have.
With Web Self Serve, ordering new devices to add to your existing fleet couldn't be easier. Any orders received by midday will be received the very next day (during normal business hours).
Already registered? log in to Web Self Serve


text:
NCI/PDQ® Health professionals: Pancreatic Neuroendocrine Tumors (Islet Cell Tumors) Treatment (PDQ®) | |||||||||||||||||||
National Cancer Institute | |||||||||||||||||||
Last Modified: June 29, 2012 |
Tumors of the endocrine pancreas are a collection of tumor cell types collectively referred to as pancreatic neuroendocrine tumors (NETs). These tumors originate in islet cells. Although they may be similar or identical in histologic appearance to carcinoid tumors of the gastrointestinal tract, differences in their underlying biology and likely differences in response to therapeutic agents suggest that they should be treated and investigated as a distinct entity. 1 They are uncommon cancers with about 1,000 new cases per year in the United States. 2 They account for 3% to 5% of pancreatic malignancies and overall have a better prognosis than the more common pancreatic exocrine tumors. 2 3 Five-year survival is about 55% when the tumors are localized and resected but only about 15% when the tumors are not resectable. 3 Overall 5-year survival rate is about 42%. 2Figure 1. Cancer of the Pancreas: Relative Survival Rates (%) by Histologic Subtype, Ages 20+, 12 SEER Areas, 1988-2001. Key, C. Ch 7: Cancer of the pancreas. In: Ries LAG, Young JL, Keel GE, et al. (eds). SEER Survival Monograph: Cancer Survival Among Adults: U.S. SEER Program, 1988-2001, Patient and Tumor Characteristics. National Cancer Institute, SEER Program, NIH Pub. No. 07-6215, Bethesda, MD, 2007. Most pancreatic NETs are sporadic, but some occur as part of the autosomal dominant multiple endocrine neoplasia type-1 (MEN-1) inherited syndrome consisting of tumors of the anterior pituitary, parathyroid, and endocrine pancreas glands, which results from the inactivation of the tumor suppressor gene Menin located on chromosome 11q13. 4 When part of the MEN-1 syndrome, there may be multiple pancreatic tumors. Islet tumors may either be functional (produce one or more active hormones) or nonfunctional. 4 The functional tumors, which usually present with symptoms of hormone hypersecretion, include:
Most islet cell cancers are functional, but about 15% are nonfunctional, with presentations similar to the far more common exocrine adenocarcinomas of the pancreas. 5 6 7 Because of the presence of several cell types in the pancreatic islets (alpha, beta, delta, A, B, C, D, E, F), the term, islet cell tumors, refers to at least five distinct cancers that, when functional, produce unique metabolic and clinical characteristics. The clinical manifestations in functional tumors may result from the distinctive metabolic effects of the polypeptide(s) secreted by the cancer cells rather than from tumor bulk or metastatic disease. Functional tumors may even be too small to be detected by conventional imaging techniques. Nonfunctional tumors tend to present at later clinical stages with symptoms attributable to mass effect or metastases. 4 Although nonfunctional tumors do not produce specific clinical syndromes, they may secrete inactive amine and peptide products such as the following:
The frequent long delays between initial symptoms and diagnosis and the varied effects of the polypeptides secreted often necessitate involvement of multiple surgical and medical subspecialties. Surgery is the only curative modality. Surgery is often used even in the setting of metastatic disease to alleviate the symptoms of hormonal hypersecretion. 4 Effective palliation may be achieved because of the slow-growing nature of the majority of these tumors and the potential use of antihormonal pharmacologic therapy (e.g., cimetidine in the ulcer-producing Zollinger-Ellison syndrome). In patients with indolent, slow-growing metastatic islet cell tumors, the best therapy may be careful observation, and no treatment until palliation is required. In patients with MEN-1 in which 85% have pancreatic islet cell tumors, 90% have hyperparathyroidism, and 65% have pituitary tumors, and they are less likely to be cured by pancreatic resection than are patients with sporadic islet cell tumors. With the exception of pain relief from bone metastases, radiation therapy has a limited role in this disease. Tumor localization and staging studies include imaging with computed tomography (CT) with or without magnetic resonance imaging (MRI), and endoscopic ultrasound. In addition, somatostatin-receptor scintigraphy and single-photon emission CT may be useful adjuncts. However, somatostatin-receptor scintigraphy has diminished utility in localizing insulinomas versus other pancreatic NETs, since insulinomas often have a low density of somatostatin receptors. 4 If the noninvasive tests do not reveal a tumor, but clinical suspicion remains high, more invasive and technically demanding tests, such as selective arteriography or selective arterial stimulation (with a secretagogue specific for the suspected tumor type), may be useful. 7 Some of the tumor types have unique characteristics that require specific approaches in their diagnosis and initial evaluation: Diagnosis is dependent on elevated serum gastrin and elevated gastric acid levels. Provocative testing with calcium and secretin shows considerable overlap, and the value of these tests is limited. Zollinger-Ellison syndrome (ZES) is a syndrome of unrelenting peptic ulcer disease, diarrhea, and gastric hyperacidity, associated with a gastrin-producing tumor. (Refer to the Diarrhea section in the PDQ® summary on Gastrointestinal Complications for more information.) It accounts for less than 1% of all peptic ulcer disease. About 15% to 35% of gastrinomas are associated with the MEN-1 syndrome and up to 50% are malignant. Up to 33% of gastrinomas have liver metastases. 4
Insulinomas are far more likely to be benign than malignant. Only 10% are multiple, and only 10% are malignant. About 5% to 8% are associated with MEN-1 syndrome. 4 The clinical manifestations are those of hypoglycemia, which results from inappropriate secretion of insulin by the tumor. Fasting hypoglycemia (<40 mg/dL) associated with an elevated insulin level (in the absence of exogenous administration of insulin) is pathognomonic. Measurement of plasma proinsulin may be helpful for diagnosing insulin-secreting carcinomas. These tumors are usually slow-growing tumors and, when localized to the pancreas or regional lymph nodes, can be cured with pancreatic resection. The approach to management depends on carefully performed preoperative localization studies and the findings at exploratory laparotomy. In a retrospective case series of 30 patients with 32 pancreatic insulinomas, the combination of preoperative dual-phase thin-section multidetector CT and endoscopic sonography correctly identified and localized all of the tumors. 8 These tests, with or without MRI, have replaced older, more invasive, and technically challenging tests, such as percutaneous transhepatic portal venous sampling and arterial stimulation with venous sampling except for unusual circumstances in which the imaging tests are unsuccessful. 4 9 Glucagonoma is the third most common endocrine-secreting islet cell tumor. About 75% of glucagonomas are malignant. 4 Necrolytic migratory erythema, hyperglycemia, and venous thrombosis comprise a virtually diagnostic triad. A serum glucagon level greater than 1000 pg/mL confirms the diagnosis. These tumors tend to be large and easily visible on CT scan. Somatostatin receptor scintigraphy scanning may be a useful adjunct in detecting metastases.
These tumors are rare but have defined clinical syndromes associated with specific production of polypeptide hormone production by islet cell tumors. Because of their rarity and similar approaches to management, they are grouped in the section on treatment. Miscellaneous tumors include the following:
Note: The American Joint Committee on Cancer has published the 7th edition of the AJCC Cancer Staging Manual, which for the first time incorporates pancreatic neuroendocrine tumors in the same staging system as pancreatic exocrine tumors. 1 The classification of these tumors as benign versus malignant is not always consistent, so the AJCC recommends that all pancreatic neuroendocrine tumors be staged using this system and reported to cancer registries. It also recommends that the protocol developed by the College of American Pathologists for endocrine pancreatic tumors be used to examine and stage specimens. 2 The American Joint Committee on Cancer has designated staging by TNM classification to define pancreatic neuroendocrine tumors (islet cell tumors). 1
Histologic Grade (G)a A two-, three-, or four-grade system may be used. If a grading system is not specified, generally the following system is used:
Check for U.S. clinical trials from NCI's list of cancer clinical trials that are now accepting patients with islet cell carcinoma. The list of clinical trials can be further narrowed by location, drug, intervention, and other criteria. General information about clinical trials is also available from the NCI Web site. References:
If technically and medically feasible, primary management of endocrine tumors of the pancreas involves surgical resection with curative intent. Given the rare nature of these tumors, surgical approaches are based upon case series and expert opinion rather than randomized controlled trials. 1 The surgical options listed below are based on retrospective series from single reporting centers. 2 3 4[Level of evidence: 3iiD or 3iiiD] Adjuvant therapy has no proven benefit and is, therefore, investigational. There have been no well-controlled trials of adjuvant therapy after complete tumor resection. 5
Surgery plays a role even in the setting of metastatic disease. The symptoms of metastatic functional pancreatic neuroendocrine tumors (NETs) may be ameliorated by the reduction of overall tumor burden through surgical debulking. The liver is a common site of metastasis from pancreatic NETs. Because of the slow growth rate of many NETs, liver metastases are often resected when technically feasible. Resection of all grossly visible liver metastases can be associated with long-term survival and, in the case of symptomatic hormonally functional tumors, symptom relief. 6 Most symptoms from functional tumors respond to this form of surgical debulking. How much of the favorable survival rates is attributable to patient selection factors is not known (e.g., underlying patient condition, extent of metastases, slow doubling time, and so forth). A variety of alternative approaches to the management of liver metastases have been reported, including gel-foam embolization or transarterial chemoembolization, 7 radioembolization with radioactive microspheres, 8 9 10 radiofrequency ablation, cryoablation, and percutaneous alcohol ablation. These alternative approaches have been reviewed. 11 Results from surgical resection series appear to be more favorable than with these techniques, and surgery is considered to be the standard approach to resectable liver metastases. However, there are no high-quality studies comparing the various approaches. A systematic review of evidence comparing liver resection versus other treatments for patients with resectable liver neuroendocrine metastases found no randomized trials, or even quasi-experimental, cohort, or case-control studies in which the patient population given the alternative therapies was similar enough to the surgery group to draw reliable conclusions. 12 The evidence for resection of all grossly visible liver metastases derives solely from case series.[Level of evidence: 3iiD or 3iiiD] In most cases, liver metastases are not completely resectable. Cytoreductive surgery, with or without radiofrequency ablation or cryoablation, has been used to palliate symptoms. A systematic review found no randomized or quasi-randomized trials comparing cytoreductive surgery to other palliative approaches such as chemotherapy or tumor product inhibitors. 13 The evidence for surgical cytoreduction of unresectable liver metastases is restricted to case series [Level of evidence: 3iiD or 3iiiD], and interpretation of outcomes may be strongly affected by patient selection factors.
Somatostatin analogs may be effective in reducing the symptoms of functional tumors. 14 Chemotherapy using drugs such as the following, either alone or in combination, has been shown to have antitumor effects, but evidence is weak or conflicting regarding the impact of chemotherapy on overall survival: 15 16 17
More recently, a variety of systemic agents have shown biologic or palliative activity, including: 5 18
Nearly all of the evidence of activity derives from case series.[Level of evidence 3iiiDiv] However, there are ongoing placebo-controlled randomized trials of everolimus 19 and sunitinib 20 that have been reported in abstract form showing an increase in progression-free survival in each case.[Level of evidence 1iDiii] Favorable responses have been reported in patients with advanced progressive pancreatic NETs after treatment with several radiolabeled somatostatin analogs in which the analogs octreotide, octreotate, lanreotide, or edotreotide are stably attached to the radionuclides 111Indium, 90Ytrium, or 177Lutrium. 21 22 23 The relative efficacy of these various compounds is unknown. Study designs have been limited to case series with tumor response, biochemical response, or symptom control as the measure of efficacy.[Level of evidence 3iiiDiv] As noted in each of the clinical situations, there is a paucity or absence of high-level evidence, and a need for randomized controlled trials. 5 Check for U.S. clinical trials from NCI's list of cancer clinical trials that are now accepting patients with islet cell carcinoma. The list of clinical trials can be further narrowed by location, drug, intervention, and other criteria. General information about clinical trials is also available from the NCI Web site. References:
The approach to treatment often depends on the results of preoperative localization studies and findings at exploratory laparotomy. At exploration, 85% of these tumors are found in the gastrinoma triangle with 40% on the surface of the pancreas and 40% outside of the pancreas. Only 15% are found within the substance of the pancreas. Percutaneous transhepatic venous sampling may occasionally provide accurate localization of single sporadic gastrinomas. Resection (enucleation of individual tumors, if technically feasible), and even excision of liver metastases, is associated with long-term cure or disease control. 1
Patients with hepatic-dominant disease and substantial symptoms caused by tumor bulk or hormone-release syndromes may benefit from procedures that reduce hepatic arterial blood flow to metastases (hepatic arterial occlusion with embolization or with chemoembolization). Such treatment may also be combined with systemic chemotherapy in selected patients. Treatment with proton pump inhibitors or H2 blocking agents may aid in control of peptic symptoms. In the era of proton pump inhibitors and H2 blocking agents, the potentially lethal hyperacidity and hypersecretory states induced by excessive gastrin production can usually be controlled. In a series of 212 patients with Zollinger-Ellison syndrome (ZES), no patients died of causes related to acid hypersecretion. Of those patients, only 2.3% had been subjected to total gastrectomy, and the cohort upon which the report was based had a long median follow-up period of 13.8 years. Although 32% of the patients died during the course of the study, only 50% of the 67 deaths were attributable to ZES-related causes. Those causes were mainly liver metastases with progressive anorexia and cachexia (67%) or secondary endocrine tumors consequent to MEN-1 syndrome. The development of bone or liver metastases (especially diffuse liver disease) or of ectopic Cushing syndrome during the study period predicted for decreased survival times. 24 Check for U.S. clinical trials from NCI's list of cancer clinical trials that are now accepting patients with gastrinoma. The list of clinical trials can be further narrowed by location, drug, intervention, and other criteria. General information about clinical trials is also available from the NCI Web site. References:
Curative surgical excision, by open laparotomy or laparoscopy, is the treatment of choice when possible. The open surgical approach is used if the tumor is suspected to be malignant, since en bloc lymphadenectomy is performed for malignant tumors without distant metastases. Intraoperative ultrasound aids the localization of tumor extent and the relationship to other anatomic structures. 1
Patients with hepatic-dominant disease and substantial symptoms caused by tumor bulk or hormone-release syndromes may benefit from procedures that reduce hepatic arterial blood flow to metastases (hepatic arterial occlusion with embolization or with chemoembolization). 6 8 9 10 11 12 Such treatment may also be combined with systemic chemotherapy in selected patients. Check for U.S. clinical trials from NCI's list of cancer clinical trials that are now accepting patients with insulinoma. The list of clinical trials can be further narrowed by location, drug, intervention, and other criteria. General information about clinical trials is also available from the NCI Web site. References:


text:
Live Chat & EventsEvent
DescriptionThis class is designed for those new to digital photography who really want to learn to use their digital camera to its fullest potential. The class will cover very basic information up to some advanced techniques. We will cover how to get out of automatic, and into creative photography. You will learn many creative photography techniques, correct exposure and good composition. Bring your camera and manual to the class. The day will be broken down into several sessions: *Introduction to digital photography *Understanding exposure with liquid light *Seeing the light *Composition *Digital workflow February 20th, workshop to start at 10am and run until 4pm. Bring sack lunch. Free, but limited space, so register at the Nature Center ahead of time. Venue
Sorry, no description available
EventList powered by schlu.net |


text:
Please enter your current email address to receive instructions on resetting your password.
Your password has been reset. Please check your email for further instructions.
You are sending a link to the page. Please completely fill out the form below.
Add an additional message below.
The URL for the page will automatically be added to your message.
Since 1990, guests from all over the globe have put their trust in Steling Events to make the most of their Williamsburg experience. Our knowledgeable staff will customize a program to meet your specific needs and through creative planning, deliver fun and excitement to your next conference or meeting. The solid relationships in which Sterling has developed over the years with area vendors and facilities, ensures that every aspect of your visit will flow seamlessly. Sterling Events offers the following services: * Tours/Guide Services * Theming and Decor * Entertainment * Casino Nights * Airport Transportation/Meet & Greet Services * Children/Spouse Programs * Offsite Dining Venues * Creative Dine-a-Rounds * Wedding Consulting
This facility meets ADA Accessibility Guidelines for wheelchair accessibility, including an accessible entrance, access to goods and services, usability of rest rooms and accessible parking and drop-off areas. For additional details, please see the ADA website.
Order your Free 2013 Virginia Travel Guide.
What's going on around Virginia? Subscribe to the Virginia eNews.
Thank You! For subscribing to the Virginia eNewsletter. You will begin receiving 2 email newsletters each month.
View Our Newsletter Archive
Online Travel Guide
Virginia Green
Weather Forecasts
Virginia iPhone Apps


text:
Help us
Contact Us
Close window
Remember Me
Password recovery
CEN LTSO Newsletter
LTSO PDF Version
LTSO IMS Package
Ask the expert
Home page
Architectures and Interfaces
AICC Package Exchange Notification Services
EU Projects
Application Profiles
Architectures and Interfaces
AICC Package Exchange Notification Services
Current Version
CEN Simple Publishing Interface
CEN Simple Query Interface
IEEE Learning Technology Systems Architecture
IMS Abstract Framework
IMS Basic Learning Tool Interoperability
IMS Digital Repositories Interoperability
IMS Enterprise Services
IMS General Web Services
IMS Learning Information Services
IMS Learning Tools Interoperability
IMS Tools Interoperability
LSAL Learning Services Architecture
OKI Open Service Interface Definitions
Open Architecture and Schools in Society
Schools Interoperability Framework
Competency Definitions
Content Aggregation
Digital Repositories
Educational Modeling Languages
Intellectual Property and Digital Rights
Learner Information
Localization and Internationalization
Platform and Media
User Interfaces
Please wait ......
AICC Package Exchange Notification Services - Overview
Terms of use
Terms of use
These contents have been obtained from the AICC Web site and edited for presentation. Please refer to the AICC Web site for additional information on terms of use.
Aviation Industry CBT Committee
The specification/guidelines
Package Exchange Notification Services
(PENS), developed by the AICC (CMI010), describes a protocol to support a notification service to announce the location of content package(s) that are available for transport. The intent is to automate the notification, transfer and delivery confirmation of content packages between tools or systems that generate content and systems that manage, publish or deliver content.
Purpose and Scope
The purpose of this specification is to fill a gap that currently exists between the creation of content packages by "content authors" and the deployment of those content packages on LMSs by "LMS administrators" where learners may ultimately have access to them. Without a specification that addresses this gap, the concept of shared content is incomplete: LMSs do not have a means to obtain newly developed, revised or updated content.
The scope of the specification is specifically constrained to the notification request, package transfer and related responses. Specifically outside the scope of this specification are mechanisms for physical deployment of content packages, content management, version control, publication or revoca-tion of content.
AICC Package Exchange Notification Services overview
Comments / Suggestions / Error reporting on this page
Please, choose an item on drop-down menu and write your text
Error reporting
AICC Package Exchange Notification Services - Summary
Terms of use
These contents have been obtained from the AICC Web site and edited for presentation. Please refer to the AICC Web site for additional information on terms of use.
The AICC PENS specification aims to provide a mechanism whereby content that is capable of being shared can be deployed and thus actually shared in practice. It describes a notification scheme that will enable a content creator's authoring system to announce that a content package is available and ready for transport from a location that it will provide.
The PENS data model may be extended in the future to include commands in addition to the current "collect" command, which is the first service to be defined. Data elements and value spaces can be extended as driven by needs and determined in the future by the community of users.
The scope of the specification is specifically constrained to the notification request, package transfer and related responses. PENS addresses neither version control nor content management; there are no PENS commands to require the recipient to remove, replace, or update existing packages or elements of packages. PENS provides a contact URI (e.g., email address) for the recipient to contact the requestor, but PENS does not prescribe a specific workflow for processing of the transferred package. PENS does not require notifications to the requestor, other than the specific obligatory confirmation. For illustrative purposes, consider a courier service as a conceptual model for PENS. Two parties may use the courier service as a means of requesting pick-up, performing transfer, and confirming delivery. However, it is not incumbent on the courier to enforce particular post-processing by the recipient. The recipient may decide to use the parcel as notification to remove something, add the parcel to stock, or replace existing stock. All post-delivery processing is determined by the recipient. The recipient sets its own policy and procedures, and may choose to notify the party that requested delivery of specific events as it sees fit to do.
Synopsis of the package exchange notification services (PENS) model:
A notification is sent from a content source (such as an authoring tool, CMS or LCMS) to a Target System (central deployment or repository system such as a CMS, LCMS or LMS).
The notification announces the availability and location of a content package that is available for transport.
The notification represents the first step in initiating the Target System workflow to transfer and import a content package.
Notification mechanism details:
Suggested notification mechanism binding:
HTTP-GET or HTTP-POST of name-value pairs.
Notification modes:
can be server-to-server, or server via browser window to server (HTTP-GET only).
Responsibilities of sender:
The content source (herein referred to as the "Client") shall arrange for the content package to be made available on a staging server. The Client shall be capable of specifying a URI that uses HTTP, or HTTPS (secure HTTP) protocols. The Client may optionally support specifying FTP and FTPS (secure FTP) protocols and the related access credentials. It is assumed that the particular configuration of the staging server may be determined by a third party and therefore is not controlled by the content developer (Client). It is further assumed that if content is staged on the server via FTP that it does not have to be retrieved via FTP, but could be retrieved via an HTTP alias. Such provisions allow cases such as the transfer to the staging location via FTP and retrieval via an HTTP equivalent or alias to the same location.
If required by the Client's system, the notification may include a password needed to access the content package.
Responsibilities of recipient of notification:
The notification recipient (herein referred to as the "server") shall be capable of sup-porting both HTTP and HTTPS protocols for the "pull" or "get" transfer of the content package from the URI provided by the Client. The server may optionally support the retrieval of packages specified with FTP or FTPS protocols and appropriate access credentials. In such cases where the server does not support one or more optional protocols, the server is obligated to return the appropriate error message regarding the requested protocol.
Comments / Suggestions / Error reporting on this page
Please, choose an item on drop-down menu and write your text
Error reporting
AICC Package Exchange Notification Services - Current Version
Terms of use
These contents have been obtained from the AICC Web site and edited for presentation. Please refer to the AICC Web site for additional information on terms of use.
CMI010 - Guidelines for Package Exchange Notification Services
Release Date:
15 March 2006
Final specification
Electronic version:
Online available in
Tracking of changes
Section 6.2:
The package-url-expiry message element requires a trailing 'Z' to comply with the intent of the PENS specification which specifies ISO 8601 format with UTC.
In the CMI010 Revision 1.0 document, the field is described as ISO 8601 with UTC, but the example does not properly show the UTC time zone code ('Z').
Comments / Suggestions / Error reporting on this page
Please, choose an item on drop-down menu and write your text
Error reporting
LTSO survey
Friend websites
As an expert
As a regular user


text:
This motel is in an amazing location - literally ten steps from a pristine beach and what is apparently one of the best surfing spots on the east coast. However, don't expect fancy accommodations here at all - the rooms are quite small and most likely haven't been updated since the 1960s. The shower was so tiny that I needed... More
- Also Known As:
- East Deck Motel Family Hotel Montauk
- East Deck Motel Family Hotel
- East Deck Hotel Family
- East Deck Motel Family Resort Montauk, New York


text:
The hotel seems secluded even though it's right in the centre of Ponza with busy streets either side. The grounds are small but tastefully planted and maintained, with driftwood sculptures and garden chairs. It's only 10 minutes' walk from the ferry terminal but they run a shuttle to and from it, which is convenient if you have heavy luggage or... More
- Also Known As:
- Grande Hotel Ponza
- Official Description (provided by the hotel):
- Welcome to the Grand Hotel Santa Domitilla, one of the most prestigious hotels on the island of Ponza and the whole Mediterranean coastline.Our elegant and refined common areas have a cool Mediterranean décor and our splendid gardens with their abundance of Mediterranean and exotic plants are surrounded by typical Ponza-style terraces.Two seawater swimming pools are hidden behind a mass of purple bougainvillea, and our fabulous Wellbeing Course winds between lemon trees and fox grapes to the picturesque Roman Grottos with their different temperatures (from 19 to 37°C), numerous hydromassage jets, and the exquisite Arabic style and chromo-therapeutic lighting of the Turkish Bath. Then there is the prestigious restaurant and wine bar, "Il Melograno", that offers gastronomic delights in wisteria draped bowers. ... more less
- Reservation Options:
- TripAdvisor is proud to partner with Booking.com and Priceline so you can book your Grande Hotel Santa Domitilla reservations with confidence. We help millions of travellers each month to find the perfect hotel for both holiday and business trips, always with the best discounts and special offers.


text:
Kohler K-4652-NG Tea Green Lustra Q2 Elongated Closed-Front Toilet Seat with Quick-Release and Quick-Attach Hinges
Item #:
Compare Our Prices
Technical Specs
Installation Guide | |
Specification Sheet | |
Approved for Commercial Use | Yes |
Bowl Shape | Elongated |
Collection | Lustra, Q2 |
Country Of Origin | USA |
Length | 17.88 |
Made in America | Yes |
Material | Plastic |
Quick Release | No |
Soft Close | No |
Theme | Commercial, Traditional / Classic |
Width | 14.19 |
Width (Inside) | 8.44 |
Product Features:
- Elongated toilet seat with lid - designed to complement a wide variety of elongated toilet designs
- This Lustra toilet seat blends with any bathroom décor
- The Q2 advantage seats feature innovative technology that makes it easy to install and clean
- Made of solid polypropylene and is resistant to staining, fading, chipping and peeling
- Seat is ergonomically contoured to provide maximum comfort to the user
- Complete with color-matched plastic hinges
Product Technologies / Benefits:
- Quick Attach: To get you fast on your way to enjoying your new toilet seat, the Quick-Attach Hardware from Kohler makes for fast and secure installation. Simply set the seat with the screws in pre-drilled installation holes, slip a wing-nut underneath and tighten from the top with a screw driver, it's that easy.
- Quick Release: This simple yet innovative technology from Kohler allows the seat to be unlatched from the toilet for easy removal and convenient cleaning with no tools required. Simply pop open the caps and gently pull the seat forward and you are ready for that detailed cleaning job that has been so difficult in the past.
- Height: 1" (measured from rim of toilet fixture to the highest point on the seat)
- Overall Length: 18-5/8" (measured from the back of the hinges to the front most part of the seat)
- Overall Width: 14-3/16" (measured from left most point to the right most point of the seat)
- Inside Length: 12-7/16" (measured from the back to the front of the inner opening of the seat)
- Inside Width: 8-7/16" (measured from the left edge to the right edge of the inner opening of the seat)
- Distance Required Between Installation Holes: 5-1/2"
- Toilet Seat Material: Sturdy plastic
- Secure mounting assembly while maintaining ease of installation
Additional Kohler Links
- View Manufacturer Warranty
- Shop All Kohler Products
- Shop All Kohler Lustra Collection Products
Our SKU: K-4652
This product is listed under the following manufacturer number(s):
Almond - K-4652-42*
Aspen Green - K-4652-96
Biscuit - K-4652-7
Black - K-4652-K4
Cashmere - K-4652-Chamois*
Chamois - K-4652-41*
Country Grey - K-4652-89*
Desert Bloom - K-4652-NY
Dune - K-4652-W2
Earthen White - K-4652-French Vanilla*
French Vanilla - K-4652-Harvest Gold*
Harvest Gold - K-4652-Heron Blue*
Heron Blue - K-4652-95
Ice Grey - K-4652-55
Innocent Blush - K-4652-12*
Jersey Cream - K-4652-Merlot*
Merlot - K-4652-33
Mexican Sand - K-4652-52*
Navy - K-4652-Parchment*
Parchment - K-4652-53
Raspberry Puree - K-4652-G9
Sandbar - K-4652-71
Seafoam Green - K-4652-6*
Skylight - K-4652-Y2
Sunlight - K-4652-Swiss Chocolate*
Swiss Chocolate - K-4652-Taupe*
Taupe - K-4652-NG*
Tea Green - K-4652-Teal*
Teal - K-4652-58
Thunder Grey - K-4652-97*
Timberline - K-4652-0
White - K-4652-45
Wild Rose
*Denotes a finish or option that has been discontinued
3 Questions from the Community
what is the maximum weight this seat holds?
what is the difference between material solid plastic and polypropylene seats?
Is this the same as 4652-0 ?
Product Reviews
Modern Elongated Close Fronted Toilet Seat from the Lustra Collection
fast order
I received my order within a couple of days and it was easy to install. Color was a perfect match!
September 25, 2011
Worth the money!
Perfect fit! Easy to install. Solid enough to sit on without any buckling! Perfect color match! Looks GREAT! Finishing touch to the whole bath! Arrived to my door in 2-3 days with regular shipping.
October 16, 2010
Exact Match Colorwise
Have what has to be one of the only blue bathrooms in the world...local stores only carried white or almond seats...this one matched perfectly. Much more comfortable than the existing wooden seat (especially after it broke!)
September 27, 2010
not a quiet closer
It looks fine but I should have bought the one that closes quietly.
July 8, 2010
good product
i order this to replace a brand new kohler toilet seat that seemed a little flimsier. while this isn't as sturdy as toilet seats of yore (we sit on top while drying off our dogs or our daughter), it can bend inward slightly. the seat fits and looks beautiful though.
October 4, 2009
1-6 of 6
The Bold Look of Kohler is more than a slogan, it is a testament to the sight and focus of the Kohler company since the late 1800's. Kohler designs its plumbing fixtures and accessories for longevity and with a focus on pleasing your senses. Kohler's attributes make its plumbing and accessories a clear choice of quality for generations to come.
Kohler Lustra Collection
With an ability to blend with any décor, the Kohler Lustra collection of toilet seats are east to install, as well as easy to clean.
Other Products In The Kohler Lustra Collection
Kohler K-4650
Lustra Elongated Open-Front Toilet Seat
$106.90$80.18(2) -
Kohler K-4670-C
Lustra Elongated Open-Front Toilet Seat with Check Hinge
$39.05$29.29(1) -
Kohler K-4662
Lustra Q2 Round Closed-Front Toilet Seat with Quick-Release and Quick Attach Hinges
$83.55$62.66(12) -
Kohler K-4679-CA
Lustra Elongated Open-Front Toilet Seat with Anti-Microbial Agent and 1" Bumpers
$90.60$67.95 -
Kohler K-4660
Lustra Round Open-Front Toilet Seat
Warranty Info
Please call or use homepage to find the service center closest to your customer for all product warranty issues. "Power Equipment can not be returned to the vendor once it has been fueled or operated."


text:
Good afternoon and Happy Spring!
I have been a very busy travel agent, booking loads of honeymoons for happy brides and grooms. I am very honored to be a part of such an important vacation for all these wonderful couples. With that, I want to thank Jessie, the Editor-in-Chief at Beautiful Bride for giving me the opportunity to write another honeymoon article. It was great fun to write about honeymoon destinations that are inspired by the cities where the magazine is published (Las Vegas, San Diego, Central Valley, Cincinnati, Orlando and my town of Atlanta).
I hope you enjoy reading it as much as I enjoyed writing it. Look for it at your favorite bridal boutique, on newsstands at Albertsons, Vons, Smiths, Target, Wal-Mart, Barnes & Noble, Borders, CVS, or Walgreens, or click here to read it now HoneymoonDestnations
Happy Travels!
My Traveling Panda
The Beautiful Bride, Summer 2013 covers


text:
The Week in Review
Headlines all week blared the latest developments in an IRS scandal, the seizure of Associated Press phone logs and hearings staged by House Republicans on last year's deadly U.S. consulate attack in Libya. Sen. Bernie Sanders criticized the IRS as "dead wrong." He faulted the Justice Department for sweeping up reporters' phone records. He dismissed the Benghazi hearings as Republicans trying to turn a tragedy to their political advantage. But where, he asked, were the news stories about the collapsing middle class, chronic unemployment and poverty in America? Sanders welcomed a Tuesday report that the deficit is shrinking. He called again on Thursday for filibuster reform to stop Republicans from using parliamentary tactics to stiff arm President Obama's nominees. And he joked on Friday about one small problem he has with an otherwise "excellent" student loan bill by Sen. Elizabeth Warren.
Continue reading The Week in Review »
Recent Business
- 05/17/13 - Student Loans
- 05/17/13 - What Can We Learn from Denmark?
- 05/16/13 - The New Normal
- 05/15/13 - Red Ink
- 05/14/13 - Young, Unemployed, and Discouraged in America
Must Read
- 05/18/13 - 60 Minutes and the Billionaire Agenda
- 05/16/13 - Cutting Social Security and Not Taxing Wall Street
- 05/15/13 - More tax lobbyists working Washington's hallways
- 05/10/13 - Carbon Dioxide Level Passes Long-Feared Milestone
- 05/08/13 - Save Lives, Ease Suffering, Prevent Billions in Wasteful Spending
- 05/23/13 - Join Sen. Sanders for an Older Americans Summit
- 06/01/13 - White River Junction: Join Sen. Sanders for a Town Meeting on Veterans Issues
- 06/01/13 - Brattleboro: Join Sen. Sanders for a Town Meeting on Veterans Issues
- 06/01/13 - Bennington: Join Sen. Sanders for a Town Meeting on Veterans Issues


text:
CHIC 170 La Chicana
hours lecture,
Letter Grade or Pass/No Pass Option
Description: This course is the study of the Chicana in American society in historical and sociological perspective. Emphasis is placed on Chicana feminist scholarship and cultural representations, border issues, resistance to patriarchy, and the search for power. This course is designed for all students interested in Chicana and Chicano studies.
Check the Online Class Schedule for information about course Prerequisites, Co-requisites, Enrollment Limitations and Advisory information .
Degree Link
This course can help you earn the following degree(s) or certificate(s):
- Chicano Studies - Associate in Arts
- Women's Studies - Certificate of Performance


text:
Wales star Sam Warburton is looking forward to "the big job" of subduing Scotland's back-row at Murrayfield this weekend.
Warburton has insisted that regaining the Wales captaincy will not be a personal motivating factor on Saturday, despite starting an Six Nations Test match for the first time in almost two years with a team-mate skippering the side.
That duty remains with his back-row colleague Ryan Jones - as it will for next week's England clash, barring injury or loss of form - after he helped orchestrate back-to-back away victories over France and Italy.
Warburton, though, is adamant he will not be distracted from his role of trying to keep Wales in title contention through collecting a third successive away win during this season's tournament.
"The Scottish back-row is very big and physical, so maybe that has influenced the decision to play me at seven," said Warburton, who has replaced Justin Tipuric after recovering from a shoulder injury.
"That is a challenge I really enjoy. Every time we play Scotland a focal point is always the battle of the back-rows because theirs is so good.
"We know it will be a big job for me, Toby (Faletau) and Ryan (Jones) to nullify their threats, but we will try to figure out a way to get the better of them over the next few days because that back-row battle is so important now in the modern game.
"I would imagine both teams will want to play at the weekend. Both teams have some pretty good backs they want to release, so the speed of ball will be interesting.
"It will be a big area for us as a team to win that back-row battle."
Wales boss Rob Howley has admitted that Warburton, who is seven years Jones' junior and has won exactly half his 72 caps, was left "disappointed" by the captaincy decision.
But Wales' 2011 World Cup skipper, who led them to Six Nations title glory and a Grand Slam last season, added: "Getting the captaincy back won't be a motivating factor. It will just be to play well for the side.
"Ryan has done a great job over the last two weeks, and I don't see any need to change the team dynamics.
"It has obviously worked for us over the last couple of weekends, but Rob's said I can still have an input. It's not just Ryan on his own - he needs other guys.
"I might look closely at the contact area and how the referee is managing that, Adam Jones the scrum and Alun-Wyn (Jones) the lineout. It just makes sense to keep Ryan as captain.
"Ryan is the best captain I've played under, so I have no qualms with him leading the side. He has a wealth of experience and tactically he's very clued in."
Warburton's return apart, Howley has made two other changes, with prop Paul James replacing an injured Gethin Jenkins and Wyn Jones preferred to Andrew Coombs at lock.
Gilbert has released a new line of rugby cleats. The Gilbert Virtuo 8S is part of the exciting new product. Check it out.
The Barbarians are one of the top invitational rugby sides with a long history and classic rugby jersey.
The Nike Tiempo is a solid rugby cleat and one of few styles still made from full-grain natural leather.
The Lions get ready for their matches with this green training jersey. It's what the players wear. Get in the Gear!
A cool looking all black rugby cleat with the high performance adidas is known for. Get in the Gear!
Wear the crest of the British and Irish Lions on your t-shirt. A great look for the summer.
The Lions are ready to get their Australia tour underway. They arrive in Perth on Monday.
The New Zealand All Blacks training jersey for 2013/14. Get in the Gear!
The USA Rugby Pro Alternate rugby jersey is perfect for any fan of the Eagles. Get yours to wear during the summer Test matches.
The NEW All Blacks 2013/14 jersey has arrived at World Rugby Shop. Dare to wear the colors of the All Blacks.


text:
What is a good bokeh, what should it be like? What affects it (lens, focus screen, camera settings, aperture of course).
"Lens manufacturers including Nikon, Canon, and Minolta make lenses designed with specific controls to change the rendering of the out-of-focus areas."
says wiki, and continues:
"The shape of the aperture has a great influence on the subjective quality of bokeh. When a lens is stopped down to something other than its maximum aperture size (minimum f-number), out-of-focus points are blurred into the polygonal shape of the aperture rather than perfect circles."
How about adapters? Which one's bokeh is the best? It is obvious that bokeh is not just a blur... My guess is, the focus screen is the key element to a good bokeh...
Adapter owners, could you post some images with a shallow DOF to let us compare?
Also, I'd like to see same adapter/different lens combinations. Could we build a reference topic? What do you say?
- baco


text:
Save 10% Today • Use Promo Code USA10
Lupine Wild West Small Dog Collar (1/2 Inch)
By Lupine
Cowboy up! Your dog will look amazing in Wild West from Lupine®. Spunky and raring to go, this a great choice for any pup. This traditional adjustable collar is 1/2" wide. Matching leash and harness are also available to complete the look.
Lupine collars are stylish, functional and extremely durable. In fact, LUPINE® products are GUARANTEED (Even If Chewed)®. If your pooch destroys a Lupine collar, simply mail it back to Lupine's headquarters and they will send you a free replacement!
See more: Dog Collars


text:
Skip to content. | Skip to navigation
Did you not find what you were looking for? Try the Advanced Search to refine your search.
Subscribe to an always-updated RSS feed.
...and SPAM!
Western religious leaders need to speak out more strongly on the dangers of climate change.
Five extraordinary women tested for seventy-five peculiar toxins.
Arguing about water is a beloved Western pastime, but as the snowpack shrinks, Coloradoans are going to find themselves seriously fighting over what's left in the Colorado River.
Environmental pioneer Stewart Udall and his wife, Lee, ask their grandchildren to be "steadfast enemies of waste."
Ernest Atencio ponders an exceptionally muddy Mud Season in New Mexico, and notes how readily most Westerners forget that we live in an arid landscape.
The West's weather is full of surprises this spring, with snowstorms, windstorms, rain and wildfires all happening at the same time.
The urgency of the politicians' response to our economic troubles contrasts with the way we're ignoring the greater crisis of climate change.
Paleo-oceanographer James Zachos points to evidence of the last time climate change acidified the oceans, some 55 million years ago.
The West in your Inbox
• The best weekly collection of Western environmental news
• An at-a-glance look at our latest news and analysis
This box was designed to only appear once. It uses a "cookie" (a small file stored on your computer) to remember that it has shown the box to you. If you are seeing this box appear multiple times, then something is not allowing the cookie to be stored properly. Browsers can be set to not allow cookies, and some people choose to disallow cookies for security reasons. If your browser is setup this way, please consider adding "www.hcn.org" as an exception to your no-cookies rule. For information about how to do this, just search the Web for "browser cookie exceptions." If you're sure this isn't the problem, then it could be related to how your browser has stored information from our site in previous visits. Browsers often "cache" images, text and other website content in order to make them appear faster if you ever go back. Sometimes the browser's cache can be corrupted or become outdated. The simplest fix for this is to try reloading the page. If that doesn't fix the problem, it may be necessary to clear your temporary items from your browser. Again, a web search will provide you with lots of options and instructions. Either way, we're sorry to hear that this box is getting in the way of your enjoyment of the HCN website. If you continue to have trouble, please contact our Subscriber Services team.


text:
The Holiday Apartment Casa Marise is located in an elegant apartment, in a central area; a few minutes' walk from St.Peter's, Piazza del Popolo and Piazza Navona. It has an entrance hall, a sitting room, a study room, one double... Plus d'informations
Prix moyen 105
Holiday Apartment Laura's Brother is a penthouse, 2 rooms (40sqm) in a building of 3 floors without elevator, with comfortable and cozy furnishings and a terrace of 20sqm It is composed of living/dining room with access to the terrace,... Plus d'informations
Prix moyen 85
Strawberry House B&B is in Rome centre, Vatican Area, in the neighborhood called Prati, which is full of shops, restaurants and cinemas. The house is located in a nice building, it offers a kitchen/dining room for guests and three... Plus d'informations
Prix moyen 100
"Sweet Holidays In Rome" is an elegant furnished apartment in Rome (2+2 adults). The apartment has an "open space" entrance; equipped kitchen; living area with sofa bed; double bedroom and an outdoor terrace overlooking the RAI... Plus d'informations
Prix moyen 77
Bed & Breakfast Daffodil in Roma San Pietro is the perfect place to spend a wonderful vacation in the heart of Rome, a few steps away from S. Peter's Basilica and the Vatican Museum, in a comfy and new B&B. The double/twin rooms for... Plus d'informations
Prix moyen 73
Holiday Apartment Residenza Barsanti, located close to the famous Trastevere district, is an elegant 70sq.m apartment. The apartment consists of a a bedroom, a living room, a kitchen and a bathroom. Holiday Apartment Residenza... Plus d'informations
Prix moyen 93
Holiday Apartment S. Pietro is an elegant apartment situated on the 9th floor of a building with lift, in the elegant Prati district. The house is composed of a big entrance/living room with double sofa bed, equipped kitchen with... Plus d'informations
Prix moyen 80
Abaco B&B is located in a typical old building in Pigneto, a characteristic district in Rome; well served by public transport allowing to reach the main places of interest in a few minutes. You'll find spacious and comfortable... Plus d'informations
Prix moyen 75
The Holiday Apartment Roma18 is located in a quiet residential area in the center of Rome, close to the Vatican City. Connected with the subway (Red Line "A") and transportation is an optimal starting point for visiting Rome. The... Plus d'informations
Prix moyen 80
The Holiday Apartment Cipro is a beautiful and newly refurbished apartment, can sleep up to six people. It is located on the first floor (with a lift), just a few minutes from the Vatican and Saint Peter's Basilica. This is the ideal... Plus d'informations
Prix moyen 110
Bed & Breakfast B-Cool Rome is a modern boutique hotel; a completely new, elegant and comfortable property located just steps from the Basilica di San Pietro, in a central but quite district. Nearby there are restaurants of all kinds,... Plus d'informations
Prix moyen 125
Bed & Breakfast Alle Porte Del Colosseo is situated in a mansion of the beginnings of '900 very connected with means of public transit, between which the metropolitan to single 300 meters from the Colosseo. The B&B offers... Plus d'informations
Prix moyen 95
The Holiday Apartment "Tutti Pazzi Per Roma House" is a beautifully and renovated apartment. The apartment consists of a triple bedroom, spacious and bright with possibility to add a free extra bed, is equipped with TV 32 "LCD. It... Plus d'informations
Prix moyen 122
The Holiday Apartment Maison di Biancaneve, situated in a modern building of Montesacro, guarantees tranquility just a few steps from the centre. Thanks to the new metro-stop B1, about 100 m. from the apartment, guests takes only 5... Plus d'informations
Prix moyen 77
Bed & Breakfast Papavista Relais is an elegant guest house recently opened, and able to accommodate any kind of customer: pilgrims visiting the Vatican City, or tourists interested in the monuments of the historic centre of Rome. It... Plus d'informations
Prix moyen 215
Bed & Breakfast The Right Place, is just a few steps away from the Vatican Museums, St. Peters Basil and Sistine chapel. It opens its windows on a unique and inimitable sight, in the cultural and tourist centre of the Capital, just a... Plus d'informations
Prix moyen 80
The Holiday Apartment "Near St Peter", completely renovated in March 2012 and furnished as a charming and modern hotel, is located in a quiet street close to St Peter. The house is bright and quiet, it consists of an entrance hall, two... Plus d'informations
Prix moyen 300
The Holiday Apartment Attic is located in Prati, one of the most characteristic and lively areas of Rome; just a few meters from the Vatican Museums and St. Peter's Basilica. The apartment consists of an entrance hall, living room... Plus d'informations
Prix moyen 140
Welcome at the B&B Lost in Rome! We're located in an elegant 1930's building, on the last floor with lift. The house interiors have been restored with modern, warm and elegant furniture. It provides guests with a comfortable and... Plus d'informations
Prix moyen 100
Residence Porta Maggiore consists in apartments situated on the third floor of a residential complex, recently redecorated. It offers apartments accurately furnished, modern, welcoming, bright and equipped with every comfort. The... Plus d'informations
Prix moyen 135