The 31st meridian west is a line of longitude that is 31 degrees west of the Prime Meridian, which runs through Greenwich, London. It is an imaginary vertical line that extends from the North Pole to the South Pole. Geographically, this meridian passes through several countries in Africa, including parts of Algeria, Libya, and more. It is often used in various geographic, navigational, and mapping contexts to define locations and boundaries.
The 47th meridian east is a line of longitude that is 47 degrees east of the Prime Meridian, which is located at 0 degrees longitude. This meridian runs from the North Pole to the South Pole, passing through several countries. In the northern hemisphere, it traverses regions in countries such as Russia, and in the southern hemisphere, it passes through countries including Kazakhstan and may also touch parts of the Indian Ocean.
The 49th meridian west is a line of longitude that is located 49 degrees west of the Prime Meridian, which is the reference line for 0 degrees longitude. This meridian runs from the North Pole to the South Pole, passing through various countries and regions. In North America, the 49th meridian west serves as a significant boundary between the United States and Canada in several areas.
The 62nd meridian west is a line of longitude that is 62 degrees west of the Prime Meridian, which is located at 0 degrees longitude. It runs from the North Pole to the South Pole, crossing various countries and regions in the Western Hemisphere. In the Northern Hemisphere, the 62nd meridian west crosses parts of Canada, particularly in the provinces of Newfoundland and Labrador, as well as Quebec.
The 5th meridian west is a line of longitude that is located 5 degrees west of the Prime Meridian, which is designated as 0 degrees longitude. It runs from the North Pole to the South Pole and passes through various countries. In terms of geographical coverage, the 5th meridian west passes through several countries in Europe and Africa.
The 61st meridian west is a line of longitude located 61 degrees west of the Prime Meridian, which is the line of longitude defined as 0 degrees. This meridian runs from the North Pole to the South Pole, passing through several countries in the Americas, particularly Canada and the United States. In Canada, it crosses regions of Newfoundland and Labrador, and in the United States, it passes through parts of the state of Maine.
The 83rd meridian west is a line of longitude located 83 degrees west of the Prime Meridian, which is the reference line for longitude that runs through Greenwich, England. The 83rd meridian west runs from the North Pole to the South Pole, passing through North America, specifically the United States and parts of Canada. In the United States, the 83rd meridian west notably passes through states such as Ohio and Michigan.
The 85th meridian east is a line of longitude that is located 85 degrees east of the Prime Meridian, which is defined as 0 degrees longitude. It runs from the North Pole to the South Pole and is used in geographical coordinate systems to specify locations on the Earth's surface. In terms of geography, the 85th meridian east passes through several countries, including parts of Russia, Mongolia, India, and Bangladesh.
Before:
5 master
|
4 7 my-feature HEAD
| |
3 6
|/
2
|
1Action:
git rebaseAfter:Ready to push with linear history!
7 my-feature HEAD
|
6
|
5 master
|
4
|
3
|
2
|
1Before:
7 my-feature HEAD
|
6
|
5 master
|
4
|
3
|
2
|
1Oh, commit 6 was crap:
git rebase -i HEAD~2Mark
6 to be modified.After:Better now, ready to push.
7 my-feature HEAD
|
6v2
|
5 master
|
4
|
3
|
2
|
1Oh but there are usually 2 trees: local and remote.
So you also have to learn how to observe and modify and sync with the remote tree!
But basically:to update the remote tree. And then you can use it exactly like any other branch, except you prefix them with the remote (usually
git fetchorigin/*), e.g.:origin/masteris the latest fetch of the remote version ofmasterorigin/my-featureis the latest fetch of the remote version ofmy-feature
In order to solve conflicts, you just have to understand what commit you are trying to move where.
E.g. if from:we do:what happens step by step is first 6 is moved on top of 5:and then 7 is moved on top of the new 6:
5 master
|
4 7 my-feature HEAD
| |
3 6
|/
2
|
1git rebase master6on5 HEAD
|
5 master
|
4 7 my-feature
| |
3 6
| |
2-----------------+
|
17on5 HEAD
|
6on5
|
5 master
|
4 7 my-feature
| |
3 6
| |
2-----------------+
|
17on5 my-feature HEAD
|
6on5
|
5 master
|
4
|
3
|
2
|
1Larry Pages's older brother.
It is hard to find information on this little bugger! Not a single photo online!
Carl Jr. is mentioned in a few places in the book The Google Story. The full name "Carl Victor Page Jr." is never given in that source, only "Carl Page Jr." is used. These crazy Anglo-Saxons and their semi-optional middle names!
The Google Story does not cite its sources, but it likely got much of its insider information through interviews, e.g. Chapter 2. "When Larry Met Sergey":which suggests the authors actually interviewed Carl Jr., since interviews with Carl Jr. cannot be found anywhere else on the Internet. It would be interesting to know more how they got that level of access.
Chapter 2 mentions that Carl Jr. is nine years older than Larry. Therefore, he must have been born in 1963 or 1964. It also states that Carl studied at the University of Michigan, like his father and like Larry would also do later on:Their father was a professor at the Michigan State University, which is a different university from the University of Michigan, and not in the same city, so by breaks they mean term breaks.
He also enjoyed helping Carl Jr. - who was nine years older - with his college computer homework when Carl came home from the University of Michigan during breaks.
Chapter 2 also mentions that he was working in Silicon Valley by the time their father died in 1996:
Despite his grief [for the death of their father at the early age of 58], Larry remained enrolled at Stanford. It helped that his older brother, Carl Jr., lived and worked in Silicon Valley. They had each other, so Larry wasn't left to bear the loss alone, and the two spent time together, fondly recalling their dad and reflecting on their childhood memories.
In 1997, Carl co-founded the mailing list management website eGroups together with Scott Hassan, programmer of an early version of Google when he was a research assistant at Stanford University. Carl and Scott presumably met through Larry, but we don't have a source. The company was sold to Yahoo! in 2000. The Google Story Chapter 8. "A Trickle" mentions:Carl is listed as a co-founder in the SEC filing: www.sec.gov/Archives/edgar/data/1105102/0000950149-00-000584.txt as "Carl Page". He does not appear on the 5% stockholders however, poor Carl.
Google's deal with Yahoo!] had special significance for Larry Page, since his brother, Carl Jr., also was in serious negotiations with Yahoo! over a major business transaction. The following day, June 27, Yahoo announced plans to buy eGroups, a technology firm that Carl Page had co-founded, for $413 million.
In 2006, he brought a company he founded called "Handheld Entertainment" public through a reverse merger with a shell company: archive.nytimes.com/dealbook.nytimes.com/2006/03/21/brother-of-google-co-founder-uses-shell-company-for-handheld-start-up/. "Handheld Entertainment" made an iPod competitor apparently. SEC filing: www.sec.gov/Archives/edgar/data/1309710/000095013606009480/file1.htm.
September 27, 2023 marked Google's 25 th aniversary and the page cirosantilli.com/carl-victor-page-jr had a small surge of views according to Google Analytics. On that day, this page was one of the top Google search results for "Carl Victor Page, Jr."[ref]. Wikipedia also had a large bump in searches for "Larry Page" on the same day: pageviews.wmcloud.org/?project=en.wikipedia.org&platform=all-access&agent=user&redirects=0&start=2023-09-11&end=2023-10-01&pages=Cat|Dog|Larry_Page which must be the root cause, Larry actually managed to beat "Cat" and "Dog" on that day.
Git tips The key to solve conflicts: see the two conflicting diffs by 
Ciro Santilli 40 Updated 2025-07-16
Ciro Santilli 40 Updated 2025-07-16The key to solve conflicts is:
You have to understand what are the two commits that touched a given line (one from master, one from features), and then combine them somehow.
The common ones.
Pinned article: Introduction to the OurBigBook Project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 3. Visual Studio Code extension installation.
Figure 4. Visual Studio Code extension tree navigation.
Figure 5. Web editor. You can also edit articles on the Web editor without installing anything locally.Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.Video 4. OurBigBook Visual Studio Code extension editing and navigation demo. Source. 
- Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact