text:
Archie Marries Veronica/Archie Marries Betty
From Wikipedia, the free encyclopedia
Jump to: navigation, search
hideThis article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
This article's plot summary may be too long or excessively detailed. Please help improve it by removing unnecessary details and making it more concise. (October 2009) (Learn how and when to remove this template message)
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (October 2009) (Learn how and when to remove this template message)
(Learn how and when to remove this template message)
"Archie Marries Veronica/Archie Marries Betty"
Cover of Archie 600 (Oct 2009). Art by Stan Goldberg.
Publisher
Archie Comics
Publication date
October 2009 – April 2010
Genre
Romantic comedy
Title(s)
Archie #600–606
Creative team
Writer(s)
Michael Uslan
Artist(s)
Stan Goldberg
Bob Smith
"Archie Marries Veronica/Archie Marries Betty" is an American comic book story by writer Michael Uslan and artists Stan Goldberg and Bob Smith that was originally presented in Archie # 600–606. In issues # 600–602, the story features a futuristic look into the life of Riverdale teen Archie Andrews in the years that follow his college graduation when Archie makes his ultimate decision to marry Veronica Lodge instead of Betty Cooper. In Issues # 603–605, the story switches and Archie proposes marriage to Betty instead of to Veronica. Issue #606 serves as the epilogue to the story and ties the previous six issues together.
Contents
[hide]
1 Background
2 Plot
2.1 Part 1: Archie Marries Veronica: "The Proposal"
2.1.1 Synopsis
2.2 Part 2: Archie Marries Veronica: "The Wedding"
2.2.1 Synopsis
2.3 Part 3: Archie Marries Veronica: "It's Twins!"
2.3.1 Synopsis
2.4 Part 4: Archie Marries Betty: "Will You Marry Me?"
2.4.1 Synopsis
2.5 Part 5: Archie Marries Betty: "You May Kiss The Bride!"
2.5.1 Synopsis
2.6 Part 6: Archie Marries Betty: "Happily Ever After"
2.6.1 Synopsis
2.7 Epilogue: Archie Gets Married: "Yesterday, Today, Tomorrow"
2.7.1 Synopsis
3 Spin-offs
3.1 Life with Archie: The Married Life
3.2 Archie Marries Valerie
4 Sources
Background[edit]
In May 2009, Archie Comics released plans for what they would call "The Archie Story Of The Century" and announced that Archie Andrews would ask Veronica Lodge to marry him in Archie Comics # 600,[1] the first issue of a six-part story arc detailing their engagement, marriage and life together. The publishers of Archie Comics did not expect the response they would get from readers and longtime fans telling them they made a mistake in Archie's choice. The New York Times would later reveal that the whole story is simply a fantasy and that the first half of the story would show Archie's life with Veronica, and the second half would show his life with Betty.[2]
Plot[edit]
Part 1: Archie Marries Veronica: "The Proposal"[edit]
"The Proposal" is Part 1 in the 6 issue story arc of Archie Marries Veronica/Archie Marries Betty that was originally presented in Archie # 600.[3] The story features a futuristic look into the life of Riverdale teen Archie Andrews and his subsequent engagement to Veronica Lodge after his college graduation.
Synopsis[edit]
The night before the gang's graduation from Riverdale High, The Archies play their final concert and mourn the oncoming changes. Archie comes home and after getting heat from his father about picking a college, he takes a walk down Memory Lane... literally. Archie realizes he's never walked up Memory Lane before and switches directions. After traveling through a yellow wood, Memory Lane splits into two dirt roads. He chooses the left one and "saves the right one for another day." Archie is then cast four years into the future on the eve of his college graduation. Archie soon makes it back to his house no longer wearing his high school lettermen's jacket but one that reads "State U" on the back. His mother exclaims how excited she is for her son's graduation and Fred states how he wishes Archie had majored in business instead of history and that he's still excited he's graduating from college. Archie dismisses this when Mary states that Veronica Lodge is waiting for him inside the house. He and Veronica discuss the changes in their lives, but both accept growing up.
After a successful graduation, Veronica hosts a party at her mansion with Josie and the Pussycats headlining. Archie learns that Veronica is planning to work for her father's company in either London or Hong Kong. As for the rest of the gang, Moose Mason is going to manage his uncle's burger joint on Staten Island while his girlfriend Midge Klump will be running her own nail salon in Bayonne, New Jersey. Dilton Doiley is going to M.I.T. for his doctorate in quantum mechanics, Reggie Mantle will fulfill his destiny as a used car salesman in Atlanta and Jughead Jones will stick around Riverdale grilling burgers at Pop Tate's Choklit Shoppe until he figures things out. Finally, Betty Cooper will be working as a buyer at Saks Fifth Avenue in New York City.
After the party, Archie is given a large sum of money by his parents. A few weeks later, he uses it for the down payment on an engagement ring for Veronica. He proposes to her in "Spiffany's" just as Betty and Jughead happen to walk by and witness. Veronica accepts and Betty runs weeping in an unknown direction. Jughead later chastises Archie for not telling him his plan. Eventually, Archie and Veronica tell Mr. Lodge, who accepts Archie as his future son-in-law as long as he works for Lodge Industries. Without any other jobs lined up, Archie goes along with it as his fiancee plans the biggest wedding Riverdale has ever seen.
The residents of Riverdale are overwhelmed with shock that Archie finally chose between his two favorite gals, but also concerned with Betty's well being. In the end, Veronica calls Betty and asks her to be her maid of honor. Instead of answering, Betty simply leaves the phone on her bed.
Part 2: Archie Marries Veronica: "The Wedding"[edit]
"The Wedding" is Part 2 in the 6 issue story arc of Archie Marries Veronica/Archie Marries Betty that was originally presented in Archie # 601.[4] The story features the continuation of a futuristic look into the life of Riverdale teen Archie Andrews and his wedding to longtime girlfriend Veronica Lodge.
Synopsis[edit]
Archie is preparing for his upcoming nuptials with his groomsmen, Reggie Mantle, Moose Mason, Dilton Doiley, and best man Jughead Jones. Meanwhile, Veronica is treating her bridesmaids Midge Klump, Ethel Muggs, and Nancy Woods to a day at the spa. Veronica is sad that Betty Cooper is not there. However, Betty shows up at that moment and her position as Veronica's maid of honor is cemented. Betty brings along a “friend” of hers named Henry who works with her. Ethel states that he reminds her of Archie as Betty rushes him out the door. On the eve of the wedding, Archie and Veronica discuss their future.
The big day comes and everything seems to be going as planned. All of Riverdale is attending the wedding. Before the ceremony, Archie asks Betty to take a walk with him. He tells her that she was his first friend when his family moved to Riverdale and how he always enjoyed dating her, but then Veronica moved to town. Archie tells Betty that he loves her like a sister and asks her to promise to always be his friend. Betty obliges after they tell each other they love one another.
The wedding goes smoothly. Mr. and Mrs. Lodge walk Veronica down the aisle as all of Riverdale watches. Archie and Veronica become husband and wife as Betty looks on tearfully, but happily. At the reception, Archie and Veronica share their first dance to "Sugar, Sugar", speeches are made, the cake is cut, and the bouquet is tossed. Betty catches it and walks away trying to hide her tears. Veronica catches up to her to make sure she's okay. Archie and Veronica then depart on their honeymoon to a remote island in the Caribbean owned by the Lodges.
One year later, Archie is a big executive at Lodge Enterprises. Reggie shows up and asks for a job after he's been laid off and Archie gives him a job in sales. It's obvious that he's running himself ragged with work. When he comes home exhausted, Veronica reminds him of a dinner date they have with Ethel and her fiancé. Archie is simply too tired and refuses to move, until Veronica announces that she's pregnant and he promptly faints.
Part 3: Archie Marries Veronica: "It's Twins!"[edit]
"It's Twins" is Part 3 in the 6 issue story arc of Archie Marries Veronica/Archie Marries Betty that was originally presented in Archie # 602.[5] The story features the continuation of a futuristic look into the life of Archie Andrews and Veronica Lodge as they raise a pair of fraternal twins.
Synopsis[edit]
Archie announces Veronica's pregnancy to his parents, Fred and Mary. At that moment, Jughead, Reggie, and Moose burst in with congratulations and mention the various ways they will add to "Little Archie" or "Little Veronica's" life. Archie then breaks the news to Mr. Lodge who immediately has his will changed to bestow his most prized possession, a sled named "Rosebuddy" to his grandchild.
Meanwhile, Veronica flies to New York City to meet with Betty at a run down diner. Betty hasn't been faring well in the city. She's recently been laid off and her relationship with Henry has ended because it's "hard to meet nice guys in the city." Veronica announces that she is pregnant and asks Betty to be the godmother, to which she agrees.
Two trimesters later, Archie and Veronica begin Lamaze class, which proves to be a slapstick disaster for Archie. One night when Veronica's ill, Jughead fills in for her replete with a pillow under his shirt and hilarity ensues. Despite all of this, Archie promises to be calm when the big day arrives. Shortly thereafter, Veronica goes into labor and he drives her to the hospital with minimal drama. Soon, Veronica delivers a redheaded boy named Archie, and a black haired girl named Veronica.
Time passes and Archie and Veronica move back to Riverdale and buy a minivan. Parenting is exhausting for both of them, but they lovingly raise their children past diapers and bottles. When the children are around three, the Andrews and the Lodges celebrate Christmas together. The children are sent to bed and Archie and Veronica discuss their happiness. Archie claims that he would be just as happy without the money. "All you need is love," he says.
Archie tucks his children to bed and reads them "The Road Not Taken" by Robert Frost in its entirety. Before wrapping up the rest of the presents, Archie insists on going for a walk during the first snow of the season. He and Veronica exchange "I Love You's" and he heads out the door, looking distraught. He walks up Memory Lane and comes to the yellow wood and begins walking down the right fork in the road.
Part 4: Archie Marries Betty: "Will You Marry Me?"[edit]
"Will You Marry Me?" is Part 4 in the 6 issue story arc of Archie Marries Veronica/Archie Marries Betty that was originally presented in Archie # 603.[6] The story features a futuristic look into the life of Riverdale teen Archie Andrews and his subsequent engagement to Betty Cooper after college in an alternate reality.
Synopsis[edit]
Archie, still in his winter coat from his walk during the first snow of the season, arrives back in time right before his college graduation and meets Jughead, Reggie, and Moose. He is confused at first by the summer heat and his apparent time travel. Archie then rushes home to get ready for graduation, and the ceremony proceeds much as it did in Part 1, with Dilton giving the valedictorian address. After graduation, Archie, Reggie, and Jughead drive to Pop Tate's Choklit Shoppe for a party. Reggie comments on how unlikely marriage is after college. Jughead is relieved at this statistic, but Archie seems optimistic and announces that he has finally made his choice between Veronica and Betty, but he refuses to tell “until he talks to the girls first.”
Upon entering Pop's, Betty asks Archie for a dance, but he has Veronica on the brain and Betty points him in her direction. Veronica, surrounded by a group of handsome young men, is telling about a graduation trip around the world in 80 days. Archie asks to speak with her privately and starts to reminisce about the day she moved to Riverdale, but she keeps interrupting him. Reggie and Jughead spy from afar and are unclear if he's "proposing or letting her down easy." Before anything serious can be said, Moose demands that The Archies play a few songs. Even though the group hasn't played since high school, they entertain everyone with one of their hits, “Jingle Jangle”. Moose then starts a food fight that Jughead thoroughly enjoys.
After the gang cleans up their mess, Archie attempts to resume his conversation with Veronica, but she interrupts him again to tell him she's moving to Paris after her trip to run her father's fashion holdings. After this news, Archie has no need to continue his speech and asks Betty to share a malt with him while Veronica goes back to her bastion of beaux. Archie reminds Betty of how they first met and were always friends…sometimes more. He claims he can never fit into Veronica's high society world. Betty assumes he's going to ask her to “go steady,” but he claims that's not what he's thinking. Betty beats herself up and calls herself a jerk for assuming Archie wants to just date her. Archie laughs and calls her “the nicest, most loveable and beautiful jerk in Riverdale” and then pops the question. Betty, in shock for a moment, jumps for joy and answers yes. Archie and Betty kiss as Veronica watches in awe and disgust. Midge swoons at the romantic moment and prods her longtime boyfriend, Moose for a similar proposal, but he makes a joke instead. She slams his mortarboard over his head. Meanwhile, Reggie tries to make his move on Veronica, pretending to comfort her. She also breaks his mortarboard over his head. Veronica screams at Archie, claiming he missed his chance, but Archie defends his engagement to Betty in turn claiming that "she" was the one who missed her chance with him.
Later that evening, Archie and Betty tell both their parents about the engagement. The Andrews are very pleased with their son's choice of “marrying for love, not money.” The Coopers are also very happy. Betty then tells them that they plan to have a small, inexpensive wedding at Pop Tate's. Meanwhile, Veronica cries on her father's shoulder, but he assures her that there are plenty of men out there and “things always work out for the best.” All of Riverdale is gossiping about the upcoming nuptials, and whether Veronica's fortune should be a factor. On the night of Archie's bachelor party at Pop Tate's, his groomsmen, Jughead, Reggie, Moose, Dilton, and Chuck express concern for Veronica and her place among Betty's bridesmaids. Meanwhile, Betty goes to the Lodge estate and asks Veronica to be her maid of honor, who promptly slams the door in her face. But after seeing her so upset, Veronica agrees and tells Betty "she won Archie fair and square".
Later that night, Archie and Betty go for a walk. Archie has been sending out resumes, but is finding it difficult to find a job during the recession. He apologizes for not offering a better honeymoon than at the Blue Roof Inn in Centerville. Betty is entirely satisfied with it, however, and claims it's all part of “life with Archie.”
Part 5: Archie Marries Betty: "You May Kiss The Bride!"[edit]
"You May Kiss The Bride!" is Part 5 in the 6 issue story arc of Archie Marries Veronica/Archie Marries Betty that was originally presented in Archie # 604.[7] The story features a futuristic look into the life of Archie Andrews and his wedding to Betty Cooper.
Synopsis[edit]
Archie continues to search for work with no luck. In desperation, he goes to meet with Mr. Lodge at his office. Mr. Lodge tells him that despite jilting his daughter, he thinks Archie is a bright fellow but that his company is not hiring. Archie tells Mr. Lodge that he didn't jilt Veronica, he chose Betty. Archie thanks Mr. Lodge for his time and goes back to his job search, but after applying for work everywhere from a recording studio to a coffee bar, he still has no success. In the midst of their wedding preparations, Betty reveals to Archie that she has received a job offer as a buyer for Saks 5th Avenue in New York City. She had applied before they became engaged because it was something she wanted to try, but plans to turn down the job in order to be a teacher and to be with Archie. He is shocked at first, but tells her that instead of putting everyone else first, she needs to follow her dreams for once, and decides they should move up their wedding day to the following weekend and then move to New York.
Everyone arrives to celebrate the party of the year. When Veronica arrives, escorted by Reggie, some expect trouble at first. Just as she is about to reveal the dress she bought hoping to draw attention away from the bride, the wedding cake that Betty made herself collapses and is ruined. Seeing this, Veronica decides to save the day by ordering the biggest most expensive wedding cake money can buy and changes into something she feels is more appropriate for the occasion, a waitress's uniform. Archie and Betty exchange their vows. The Bride and Groom then invite all the guests to join them in their first dance. When Betty tosses the bouquet, Miss Grundy catches it while Mr. Weatherbee looks on. The biggest surprise of the night comes when the wedding cake Veronica ordered arrives. Everyone is very proud of her, and Archie and Betty thank her for her very generous gift. Veronica asks them where they plan to go for their honeymoon, but they tell her that they can't afford one yet. She takes Archie aside and tells him that she will pay for a honeymoon for them. He thanks her for the offer but turns her down, saying that he is responsible for Betty now.
They say goodbye to their families, friends and Riverdale, and set off for New York City. Betty impresses Cassie, her new boss on her very first day on the job. Archie's efforts to find a job continue to be unsuccessful until he has a chance encounter with a club owner who is looking for someone who can play the guitar and sing. Several months pass and the Andrews attend Betty's first corporate dinner with Cassie and her boss, Mr. Hugo. When they first meet him he makes a crack about Archie's clothes and talent. Archie tries to defend himself, but Betty tries to pass it off as a joke. He tries to insult Archie again, but Betty loses it and tells him she would punch him if she wasn't as classy as her husband, and quits her job on the spot. Betty apologizes to Archie for not standing up for him sooner, and Archie calls her his hero. They decide to move back to Riverdale. The next day while packing their bags, Cassie shows up at their apartment with flowers, asking them to stay and tells Betty she still has a great future with the company. Betty thanks her and says she already has a great future with Archie back in their hometown. Cassie tells them both how lucky they are and wishes them well.
Back in Riverdale, Archie and Betty move in with Archie's parents, but Betty assures him it is temporary. She has found out from Mr. Weatherbee that a teaching position is available at Riverdale High, and lets Archie know that he wishes to speak to him about something important. Mr. Weatherbee offers him the position of the school's music teacher, and Archie accepts. That night, Archie and Betty celebrate their first anniversary with a romantic dinner and share a malt with three straws in it. Archie, confused and thinking that Veronica would be joining them, is told that the third straw isn't for her, but for someone he will love. Betty tells him she's pregnant, and Archie immediately faints.
Part 6: Archie Marries Betty: "Happily Ever After"[edit]
"Happily Ever After" is Part 6 in the 6 issue story arc of Archie Marries Veronica/Archie Marries Betty that was originally presented in Archie # 605.[8] The story features a futuristic look into the life of Archie Andrews and Betty Cooper as they raise a pair of fraternal twins.
Synopsis[edit]
Archie & Betty discover many things have changed in Riverdale in the year they were in New York City. They run into Jughead & Midge and are shocked to learn that they are now married. Moose is now the custodian at Riverdale High and practises yoga and meditation and is "at peace with his inner self." When they all decide to go for dinner, Archie and Betty learn that Pop Tate is retiring and has sold the Chok'lit Shoppe to Jughead and Midge and it has been renamed "Juggie's". At the new Juggie's, the gang runs into Veronica & Reggie, and learn they have a surprise of their own; they are engaged. On their ride home, Archie & Betty argue about the news of their friends' engagement. Archie believes it is wrong, but Betty thinks that he is wishing it was him. He assures Betty that he thinks it is wrong of them to marry because he believes it will end badly, and that he only wants her money. Betty accepts his statement and they make up.
As the next few months pass, Archie & Betty become two of the most popular teachers at Riverdale High, and as Betty's pregnancy advances, they start to have less time for the rest of the old gang. Then one fall day, as Archie plans to go for a bike ride, Betty goes into labor while he goes into a panic. Instead of calling an ambulance, Archie calls the water department. Archie then drives Betty to the hospital, but they end up getting a flat tire. Luckily, Archie had his bike in the trunk, and takes her the rest of the way by bike. After a few misunderstandings at the admitting desk, Betty is rushed to the maternity ward, and soon gives birth to twins; a red haired boy named Archie and a blonde haired girl named Betty. Soon, Mr. & Mrs. Cooper and Mr. & Mrs. Andrews arrive along with all their friends and colleagues. Archie and Betty ask Jughead, Veronica and Reggie to be the twins' godparents, while Reggie & Veronica ask them to be their best man and maid of honor at their wedding. The next weekend they fly the whole gang out to Las Vegas for the star studded ceremony.
As Archie & Betty adjust to parenthood, life goes on in Riverdale. Jughead & Midge are soon expecting a child of their own. Mr. Weatherbee & Miss Grundy along with Miss Beazley & Mr. Svenson have started dating. Archie & Betty receive a postcard from Veronica & Reggie detailing all of their world travels and new ventures. Betty comments to him that could have been his life, but Archie tells her he doesn't want that life when he already has the best life with her. Betty suggests they go to bed early, but Archie says he's not tired and decides to go for a walk in the woods. He tells her not to wait up, and she says she'll be waiting no matter how long. He then decides to walk up Memory Lane, and soon finds himself back in the present... he is once again a teenager.
On his way home, he runs into Jughead who reminds him of the poetry recital in Miss Grundy's class the next day. Archie tells him he worries too much, while Jughead tells him to be prepared. As the two best friends walk home, he reads his part of the poetry reading, the last stanza of "The Road Not Taken" by Robert Frost.
Epilogue: Archie Gets Married: "Yesterday, Today, Tomorrow"[edit]
"Yesterday, Today, Tomorrow" is the epilogue that ties together Part 1 through 6 of the Archie Marries Veronica/Archie Marries Betty storyline that was originally presented in Archie #606. Archie is left in a vision of the future and struggles to explain it to his friends... and Betty and Veronica.
Synopsis[edit]
After his experiences walking up Memory Lane, Archie is left in a bewildered state. He tries talking about it to Betty and Veronica, but they are both too busy to talk to him. Needing to talk to someone about it he tells Reggie and Jughead about his strange visions. Reggie immediately thinks that he has gone nuts, but Jughead believes him.
In order to clear his mind Archie decides to go bowling with Reggie and Jughead. When Betty arrives Archie asks her if she wants to go on a date Saturday night, which she accepts. However, as he was overwhelmed with a kiss moments ago, Archie somehow mishears Betty and thinks she said "Friday". Later he goes to Lodge Mansion to ask Veronica for a date on the same night and she says yes.
When Saturday night arrives Archie realizes he asked both Betty and Veronica out on the same night. When the girls find out they respond by pouring two milkshakes on his head. The next day, Betty and Veronica are still mad at Archie, but he vows that he will make it up to both of them. When talking about the future, Archie asks Jughead if he ever thought about buying Pop's place after he retires. Jughead however denies this, because he would have to think about the future and prefers to live in the present.
Spin-offs[edit]
The success of the Archie Marries Veronica/Archie Marries Betty storyline led to the comic series, Life with Archie: The Married Life, and a similar storyline called "Archie Marries Valerie", depicting Archie marrying Valerie from Josie and the Pussycats, shown in Archie #631-634.
Life with Archie: The Married Life[edit]
Life with Archie: The Married Life was based on the Archie Marries Veronica/Archie Marries Betty storyline, but was not a direct continuation on it. The series lasted from 2010 to 2014, ending with 37 issues. Issues 1-35 contained two stories each, the first story was Archie Marries Veronica and the second one was Archie Marries Betty. The last two issues, on the other hand, were structured differently. Instead of having two stories both issues had one, but were twice as long as the others. Also, neither issue made it clear whether Archie was married to Betty or Veronica. Together both issues make up The Death of Archie storyline.
Archie Marries Valerie[edit]
The "Archie Marries Valerie" storyline was similar to the Archie Marries Veronica/Archie Marries Betty storyline, but had some major differences. For instance, Valerie was the one who walked up Memory Lane instead of Archie and she could see the future in portals rather than actually experiencing it. She sees a future in where she marries Archie, then they both quit their respective bands due to their touring schedules keeping them apart, and later have a little girl named Star who is gifted with her parents' musical talent. However, she decides to stop watching it after she sees that they cannot get a moment's peace due to Star becoming an object of attention for the media. Then she witness glimpses of other futures and in each one Archie is married to a different woman. Some of these futures had Archie being married to Cheryl Blossom, Sabrina Spellman, and even Josie. Seeing these futures Valerie runs out of Memory Lane and happily reunites with Archie.
Sources[edit]
Jump up ^ "Comic suspense: Archie Andrews pops question". CNN.com. 2009-05-28. Archived from the original on April 8, 2010. Retrieved 2010-12-27.
Jump up ^ "This time, Archie plans to marry Betty". .canada.com. 2009-10-07. Retrieved 2010-12-27.
Jump up ^ Issue no. 600, October 2009
Jump up ^ Issue no. 601, November 2009
Jump up ^ Issue no. 602, December 2009
Jump up ^ Issue no. 603, January 2010
Jump up ^ Issue no. 604, February 2010
Jump up ^ Issue no. 605, March 2010
[hide]
v
t
e
Archie Comics publications
Imprints
Mighty Comics/Red Circle Comics/Dark Circle Comics
Archie Horror
Archies
Archie
Archie (2 volumes)
Little Archie
Life with Archie (2 volumes)
Archie and Me
Everything's Archie
Archie at Riverdale High
Archie Meets the Punisher
Afterlife with Archie
Archie vs. Predator
Archie vs. Sharknado
Archie (comic strip)
Betty and Veronica
Archie's Girls Betty and Veronica
Jughead
Archie's Pal Jughead Comics (2 volumes)
Jughead (3 volumes)
Jughead's Double Digest
Reggie
Archie's Rival Reggie
Reggie
Reggie and Me
Anthologies
Laugh Comics (2 volumes)
Pep Comics
Archie's Pals 'n' Gals
Archie's Mad House
Archie Giant Series
Laugh Comics Digest
Archie's TV Laugh-Out
Archie Americana Series
Archie's Holiday Fun Digest
Tales from Riverdale
Related titles
Josie and The Pussycats (2 volumes)
Sabrina the Teenage Witch (2 volumes)
Sabrina
Chilling Adventures of Sabrina
See also
New Riverdale
Licensed
properties
Sonic
Sonic the Hedgehog
issues
Knuckles the Echidna
Sonic X
Sonic Universe
Teenage Mutant
Ninja Turtles
Teenage Mutant Ninja Turtles Adventures (3 volumes)
Mighty Mutanimals (2 volumes)
Other
Wild West C.O.W.-Boys of Moo Mesa (2 volumes)
Street Sharks (2 volumes)
Nights into Dreams
Mega Man
Superhero
Blue Ribbon Comics (2 volumes)
Top-Notch Comics
Shield-Wizard Comics
Zip Comics
Hangman Comics
Black Hood Comics
The Adventures of The Fly
Adventures of the Jaguar
Fly Man
Mighty Crusaders (2 volumes)
Black Hood
The Comet
Anthologies
Pep Comics
Jackpot Comics
Others
Super Duck Comics
Wilbur Comics
Katy Keene (2 volumes)
Li'l Jinx
Cosmo the Merry Martian
That Wilkin Boy
Storylines
"Archie Marries Veronica/Archie Marries Betty"
"Bad Boy Trouble"
"Love Showdown"
See also: List of Sabrina, the Teenage Witch books, CDs and DVDs
Spire Christian Comics
Retrieved from "https://en.wikipedia.org/w/index.php?title=Archie_Marries_Veronica/Archie_Marries_Betty&oldid=800873614"
Categories:
Storylines in comics
2009 in comics
Humor comics
Romance comics
Archie Comics titles
Works about wedding
Hidden categories:
Wikipedia articles with plot summary needing attention from October 2009
All Wikipedia articles with plot summary needing attention
Articles needing additional references from October 2009
All articles needing additional references
Articles with multiple maintenance issues
Comics infobox image less alt text
Story arc pop
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Add links
This page was last edited on 16 September 2017, at 05:57.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

value: mw-page-base noprint

value: mw-head-base noprint

value: firstHeading firstHeading en

value: siteSub noprint

value: jump-to-nav mw-jump

attr: class role tabindex

attr: class href

value: Talk:Archie Marries Veronica/Archie Marries Betty

tag: small

value: plainlinks metadata ambox ambox-style ambox-Plot

value: Help:Introduction to referencing with Wiki Markup/1

value: plainlinks metadata ambox ambox-content ambox-Refimprove

value:
mw-collapsible
width:95%; margin: 0.2em 0;

value: plainlinks metadata ambox ambox-content ambox-multiple_issues compact-ambox

value:
/wiki/Archie_(comics)
mw-redirect
Archie (comics)

value: width:22em;width: 24em; background: #f2f9ff;

value:
/wiki/Michael_Uslan
mw-redirect
Michael Uslan

value:
/wiki/Archie_Andrews_(comics)
mw-redirect
Archie Andrews (comics)

value:
/wiki/New_York_Times
mw-redirect
New York Times

value: Edit section: Part 1: Archie Marries Veronica: "The Proposal"

value:
/wiki/The_Road_Not_Taken_(poem)
mw-redirect
The Road Not Taken (poem)

value: Edit section: Part 2: Archie Marries Veronica: "The Wedding"

value:
/wiki/Maid_of_honor
mw-redirect
Maid of honor

value: Edit section: Part 3: Archie Marries Veronica: "It's Twins!"

value:
/wiki/Fraternal_twins
mw-redirect
Fraternal twins

value: Edit section: Part 4: Archie Marries Betty: "Will You Marry Me?"

value:
/wiki/Pop_Tate_(Archie_Comics)
mw-redirect
Pop Tate (Archie Comics)

value: Edit section: Part 5: Archie Marries Betty: "You May Kiss The Bride!"

value:
/wiki/Saks_5th_Avenue
mw-redirect
Saks 5th Avenue

value: Edit section: Part 6: Archie Marries Betty: "Happily Ever After"

value: Edit section: Epilogue: Archie Gets Married: "Yesterday, Today, Tomorrow"

value: Edit section: Life with Archie: The Married Life

value:
reflist mw-references-wrap
list-style-type: decimal;

value:
/wiki/Archie%27s_Rival_Reggie
mw-redirect
Archie's Rival Reggie

value: List of Archie Comics' Sonic the Hedgehog publications

value:
/wiki/Sonic_X_(comics)
mw-redirect
Sonic X (comics)

value: nowraplinks hlist collapsible autocollapse navbox-inner

value: Category:Wikipedia articles with plot summary needing attention from October 2009

value: Category:All Wikipedia articles with plot summary needing attention

value: Category:Articles needing additional references from October 2009

value: Category:All articles needing additional references

value: Category:Articles with multiple maintenance issues

value: Category:Comics infobox image less alt text

value: Discussion about edits from this IP address [ctrl-alt-n]

value: A list of edits made from this IP address [ctrl-alt-y]

value: You are encouraged to create an account and log in; however, it is not mandatory

value: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

value: Discussion about the content page [ctrl-alt-t]

value: p-namespaces navigation vectorTabs p-namespaces-label

value:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

value: Past revisions of this page [ctrl-alt-h]

value: p-views navigation vectorTabs p-views-label

value:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

value:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

value:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

value: Featured content – the best of Wikipedia

value: Find background information on current events

value:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

value: portal navigation p-navigation p-navigation-label

value: Guidance on how to use and edit Wikipedia

value: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Archie_Marries_Veronica_Archie_Marries_Betty rootpage-Archie_Marries_Veronica_Archie_Marries_Betty skin-vector action-view


text:
Git
From Wikipedia, the free encyclopedia
Jump to: navigation, search
For other uses, see Git (disambiguation).
Git
A command-line session showing repository creation, addition of a file, and remote synchronization
Original author(s)
Linus Torvalds[1]
Developer(s)
Junio Hamano and others[2]
Initial release
7 April 2005; 12 years ago (2005-04-07)
Stable release
2.16.1 / 22 January 2018; 2 days ago (2018-01-22)[3]
Repository
github.com/git/git
Development status
Active
Written in
C, Shell, Perl, Tcl, Python[4]
Operating system
POSIX: Linux, Windows, macOS
Platform
IA-32, x86-64
Available in
English
Type
Version control
License
GNU GPL v2[5] and GNU LGPL v2.1[6]
Website
git-scm.com
Git (/ɡɪt/[7]) is a version control system for tracking changes in computer files and coordinating work on those files among multiple people. It is primarily used for source code management in software development,[8] but it can be used to keep track of changes in any set of files. As a distributed revision control system it is aimed at speed,[9] data integrity,[10] and support for distributed, non-linear workflows.[11]
Git was created by Linus Torvalds in 2005 for development of the Linux kernel, with other kernel developers contributing to its initial development.[12] Its current maintainer since 2005 is Junio Hamano.
As with most other distributed version control systems, and unlike most client–server systems, every Git directory on every computer is a full-fledged repository with complete history and full version tracking abilities, independent of network access or a central server.[13]
Git is free software distributed under the terms of the GNU General Public License version 2.
Contents
[hide]
1 History
1.1 Releases
2 Design
2.1 Characteristics
2.2 Data structures
2.3 References
3 Implementations
4 Web interfaces
5 Git server
6 Adoption
7 Security
8 See also
9 References
10 External links
History[edit]
Git development began in April 2005, after many developers of the Linux kernel gave up access to BitKeeper, a proprietary source control management (SCM) system that they had formerly used to maintain the project.[14] The copyright holder of BitKeeper, Larry McVoy, had withdrawn free use of the product after claiming that Andrew Tridgell had reverse-engineered the BitKeeper protocols.[15] (The same incident would also spur the creation of another version control system, Mercurial.)
Linus Torvalds wanted a distributed system that he could use like BitKeeper, but none of the available free systems met his needs, especially for performance. Torvalds cited an example of a source-control management system needing 30 seconds to apply a patch and update all associated metadata, and noted that this would not scale to the needs of Linux kernel development, where syncing with fellow maintainers could require 250 such actions at once. For his design criteria, he specified that patching should take no more than three seconds,[9] and added three more points:
Take Concurrent Versions System (CVS) as an example of what not to do; if in doubt, make the exact opposite decision[11]
Support a distributed, BitKeeper-like workflow[11]
Include very strong safeguards against corruption, either accidental or malicious[10]
These criteria eliminated every then-extant version control system except Monotone. Performance considerations excluded it, too.[11] So immediately after the 2.6.12-rc2 Linux kernel development release, Torvalds set out to write his own system.[11]
Torvalds quipped about the name git (which means unpleasant person in British English slang): "I'm an egotistical bastard, and I name all my projects after myself. First 'Linux', now 'git'."[16][17] The man page describes Git as "the stupid content tracker".[18] The readme file of the source code elaborates further:[19]
The name "git" was given by Linus Torvalds when he wrote the very
first version. He described the tool as "the stupid content tracker"
and the name as (depending on your way):

 - random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of shit": when it breaks
The development of Git began on 3 April 2005.[20] Torvalds announced the project on 6 April;[21] it became self-hosting as of 7 April.[20] The first merge of multiple branches took place on 18 April.[22] Torvalds achieved his performance goals; on 29 April, the nascent Git was benchmarked recording patches to the Linux kernel tree at the rate of 6.7 patches per second.[23] On 16 June Git managed the kernel 2.6.12 release.[24]
Torvalds turned over maintenance on 26 July 2005 to Junio Hamano, a major contributor to the project.[25] Hamano was responsible for the 1.0 release on 21 December 2005, and remains the project's maintainer.[26]
Releases[edit]
Version
Original release date[citation needed]
Latest version
Release date[citation needed]
Old version, no longer supported: 0.99 2005-07-11 0.99.9n 2005-12-15
Old version, no longer supported: 1.0 2005-12-21 1.0.13 2006-01-27
Old version, no longer supported: 1.1 2006-01-08 1.1.6 2006-01-30
Old version, no longer supported: 1.2 2006-02-12 1.2.6 2006-04-08
Old version, no longer supported: 1.3 2006-04-18 1.3.3 2006-05-16
Old version, no longer supported: 1.4 2006-06-10 1.4.4.5 2008-07-16
Old version, no longer supported: 1.5 2007-02-14 1.5.6.6 2008-12-17
Old version, no longer supported: 1.6 2008-08-17 1.6.6.3 2010-12-15
Old version, no longer supported: 1.7 2010-02-13 1.7.12.4 2012-10-17
Old version, no longer supported: 1.8 2012-10-21 1.8.5.6 2014-12-17
Old version, no longer supported: 1.9 2014-02-14 1.9.5 2014-12-17
Old version, no longer supported: 2.0 2014-05-28 2.0.5 2014-12-17
Old version, no longer supported: 2.1 2014-08-16 2.1.4 2014-12-17
Old version, no longer supported: 2.2 2014-11-26 2.2.3 2015-09-04
Old version, no longer supported: 2.3 2015-02-05 2.3.10 2015-09-29
Older version, yet still supported: 2.4 2015-04-30 2.4.12 2017-05-05
Older version, yet still supported: 2.5 2015-07-27 2.5.6 2017-05-05
Older version, yet still supported: 2.6 2015-09-28 2.6.7 2017-05-05
Older version, yet still supported: 2.7 2015-10-04 2.7.5 2017-05-05
Older version, yet still supported: 2.8 2016-03-28 2.8.5 2017-05-05
Older version, yet still supported: 2.9 2016-06-13 2.9.4 2017-05-05
Older version, yet still supported: 2.10 2016-09-02 2.10.3 2017-05-05
Older version, yet still supported: 2.11 2016-11-29 2.11.2 2017-05-05
Older version, yet still supported: 2.12 2017-02-24 2.12.3 2017-05-05
Older version, yet still supported: 2.13 2017-05-10 2.13.4 2017-08-01
Older version, yet still supported: 2.14 2017-08-04 2.14.3 2017-10-24
Older version, yet still supported: 2.15 2017-10-30 2.15.1 2017-11-28
Current stable version: 2.16 2018-01-17 2.16.0 2018-01-17
Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release
Design[edit]
Git's design was inspired by BitKeeper and Monotone.[27][28] Git was originally designed as a low-level version control system engine on top of which others could write front ends, such as Cogito or StGIT.[28] The core Git project has since become a complete version control system that is usable directly.[29] While strongly influenced by BitKeeper, Torvalds deliberately avoided conventional approaches, leading to a unique design.[30]
Characteristics[edit]
Git's design is a synthesis of Torvalds's experience with Linux in maintaining a large distributed development project, along with his intimate knowledge of file system performance gained from the same project and the urgent need to produce a working system in short order. These influences led to the following implementation choices[citation needed]:
Strong support for non-linear development
Git supports rapid branching and merging, and includes specific tools for visualizing and navigating a non-linear development history. In Git, a core assumption is that a change will be merged more often than it is written, as it is passed around to various reviewers. In Git, branches are very lightweight: a branch is only a reference to one commit. With its parental commits, the full branch structure can be constructed.
Distributed development
Like Darcs, BitKeeper, Mercurial, SVK, Bazaar, and Monotone, Git gives each developer a local copy of the full development history and changes are copied from one such repository to another. These changes are imported as added development branches, and can be merged in the same way as a locally developed branch.
Compatibility with existent systems and protocols
Repositories can be published via Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), rsync (removed in Git 2.8.0[31]), or a Git protocol over either a plain socket, or Secure Shell (ssh). Git also has a CVS server emulation, which enables the use of extant CVS clients and IDE plugins to access Git repositories. Subversion and svk repositories can be used directly with git-svn.
Efficient handling of large projects
Torvalds has described Git as being very fast and scalable,[32] and performance tests done by Mozilla[33] showed it was an order of magnitude faster than some version control systems, and fetching version history from a locally stored repository can be one hundred times faster than fetching it from the remote server.[34]
Cryptographic authentication of history
The Git history is stored in such a way that the ID of a particular version (a commit in Git terms) depends upon the complete development history leading up to that commit. Once it is published, it is not possible to change the old versions without it being noticed. The structure is similar to a Merkle tree, but with added data at the nodes and leaves.[35] (Mercurial and Monotone also have this property.)
Toolkit-based design
Git was designed as a set of programs written in C, and several shell scripts that provide wrappers around those programs.[36] Although most of those scripts have since been rewritten in C for speed and portability, the design remains, and it is easy to chain the components together.[37]
Pluggable merge strategies
As part of its toolkit design, Git has a well-defined model of an incomplete merge, and it has multiple algorithms for completing it, culminating in telling the user that it is unable to complete the merge automatically and that manual editing is needed.
Garbage accumulates until collected
Aborting operations or backing out changes will leave useless dangling objects in the database. These are generally a small fraction of the continuously growing history of wanted objects. Git will automatically perform garbage collection when enough loose objects have been created in the repository. Garbage collection can be called explicitly using git gc --prune.[38]
Periodic explicit object packing
Git stores each newly created object as a separate file. Although individually compressed, this takes a great deal of space and is inefficient. This is solved by the use of packs that store a large number of objects delta-compressed among themselves in one file (or network byte stream) called a packfile. Packs are compressed using the heuristic that files with the same name are probably similar, but do not depend on it for correctness. A corresponding index file is created for each packfile, telling the offset of each object in the packfile. Newly created objects (with newly added history) are still stored as single objects and periodic repacking is needed to maintain space efficiency. The process of packing the repository can be very computationally costly. By allowing objects to exist in the repository in a loose but quickly generated format, Git allows the costly pack operation to be deferred until later, when time matters less, e.g., the end of a work day. Git does periodic repacking automatically but manual repacking is also possible with the git gc command. For data integrity, both the packfile and its index have an SHA-1 checksum inside and the file name of the packfile also contains an SHA-1 checksum. To check the integrity of a repository, run the git fsck command.
Another property of Git is that it snapshots directory trees of files. The earliest systems for tracking versions of source code, Source Code Control System (SCCS) and Revision Control System (RCS), worked on individual files and emphasized the space savings to be gained from interleaved deltas (SCCS) or delta encoding (RCS) the (mostly similar) versions. Later revision control systems maintained this notion of a file having an identity across multiple revisions of a project. However, Torvalds rejected this concept.[39] Consequently, Git does not explicitly record file revision relationships at any level below the source code tree.
These implicit revision relationships have some significant consequences:
It is slightly more costly to examine the change history of one file than the whole project.[40] To obtain a history of changes affecting a given file, Git must walk the global history and then determine whether each change modified that file. This method of examining history does, however, let Git produce with equal efficiency a single history showing the changes to an arbitrary set of files. For example, a subdirectory of the source tree plus an associated global header file is a very common case.
Renames are handled implicitly rather than explicitly. A common complaint with CVS is that it uses the name of a file to identify its revision history, so moving or renaming a file is not possible without either interrupting its history, or renaming the history and thereby making the history inaccurate. Most post-CVS revision control systems solve this by giving a file a unique long-lived name (analogous to an inode number) that survives renaming. Git does not record such an identifier, and this is claimed as an advantage.[41][42] Source code files are sometimes split or merged, or simply renamed,[43] and recording this as a simple rename would freeze an inaccurate description of what happened in the (immutable) history. Git addresses the issue by detecting renames while browsing the history of snapshots rather than recording it when making the snapshot.[44] (Briefly, given a file in revision N, a file of the same name in revision N−1 is its default ancestor. However, when there is no like-named file in revision N−1, Git searches for a file that existed only in revision N−1 and is very similar to the new file.) However, it does require more CPU-intensive work every time the history is reviewed, and several options to adjust the heuristics are available. This mechanism does not always work; sometimes a file that is renamed with changes in the same commit is read as a deletion of the old file and the creation of a new file. Developers can work around this limitation by committing the rename and the changes separately.
Git implements several merging strategies; a non-default strategy can be selected at merge time:[45]
resolve: the traditional three-way merge algorithm.
recursive: This is the default when pulling or merging one branch, and is a variant of the three-way merge algorithm.
When there are more than one common ancestors that can be used for three-way merge, it creates a merged tree of the common ancestors and uses that as the reference tree for the three-way merge. This has been reported to result in fewer merge conflicts without causing mis-merges by tests done on prior merge commits taken from Linux 2.6 kernel development history. Also, this can detect and handle merges involving renames.
—  Linus Torvalds[46]
octopus: This is the default when merging more than two heads.
Data structures[edit]
Git's primitives are not inherently a source-code management system. Torvalds explains,[47]
In many ways you can just see git as a filesystem – it's content-addressable, and it has a notion of versioning, but I really really designed it coming at the problem from the viewpoint of a filesystem person (hey, kernels is what I do), and I actually have absolutely zero interest in creating a traditional SCM system.
From this initial design approach, Git has developed the full set of features expected of a traditional SCM,[29] with features mostly being created as needed, then refined and extended over time.
Some data flows and storage levels in the Git revision control system.
Git has two data structures: a mutable index (also called stage or cache) that caches information about the working directory and the next revision to be committed; and an immutable, append-only object database.
The index serves as connection point between the object database and the working tree.
The object database contains four types of objects:
A blob (binary large object) is the content of a file. Blobs have no proper file name, time stamps, or other metadata. (A blob's name internally is a hash of its content.)
A tree object is the equivalent of a directory. It contains a list of file names, each with some type bits and a reference to a blob or tree object that is that file, symbolic link, or directory's contents. These objects are a snapshot of the source tree. (In whole, this comprises a Merkle Tree, meaning that only a single hash for the root tree is sufficient and actually used in commits to exactly pinpoint to the exact state of whole tree structures of any number of sub-directories and files.)
A commit object links tree objects together into a history. It contains the name of a tree object (of the top-level source directory), a time stamp, a log message, and the names of zero or more parent commit objects.
A tag object is a container that contains a reference to another object and can hold added meta-data related to another object. Most commonly, it is used to store a digital signature of a commit object corresponding to a particular release of the data being tracked by Git.
Each object is identified by a SHA-1 hash of its contents. Git computes the hash, and uses this value for the object's name. The object is put into a directory matching the first two characters of its hash. The rest of the hash is used as the file name for that object.
Git stores each revision of a file as a unique blob. The relationships between the blobs can be found through examining the tree and commit objects. Newly added objects are stored in their entirety using zlib compression. This can consume a large amount of disk space quickly, so objects can be combined into packs, which use delta compression to save space, storing blobs as their changes relative to other blobs.
Git servers typically listen on TCP port 9418.[48]
References[edit]
Every object in the Git database which is not referred to may be cleaned up by using a garbage collection command, or automatically. An object may be referenced by another object, or an explicit reference. Git knows different types of references. The commands to create, move, and delete references vary. "git show-ref" lists all references. Some types are:
heads: refers to an object locally
remotes: refers to an object which exists in a remote repository
stash: refers to an object not yet committed
meta: e.g. a configuration in a bare repository, user rights; the refs/meta/config namespace was introduced resp gets used by Gerrit[clarification needed][49]
tags: see above
Implementations[edit]
gitg is a graphical front-end using GTK+
Git is primarily developed on Linux, although it also supports most major operating systems including BSD, Solaris, macOS, and Windows.[50]
The first Microsoft Windows port of Git was primarily a Linux emulation framework that hosts the Linux version. Installing Git under Windows creates a similarly named Program Files directory containing the MinGW port of the GNU Compiler Collection, Perl 5, msys2.0 (itself a fork of Cygwin, a Unix-like emulation environment for Windows) and various other Windows ports or emulations of Linux utilities and libraries. Currently native Windows builds of Git are distributed as 32 and 64-bit installers.[51]
The JGit implementation of Git is a pure Java software library, designed to be embedded in any Java application. JGit is used in the Gerrit code review tool and in EGit, a Git client for the Eclipse IDE.[52]
The Dulwich implementation of Git is a pure Python software component for Python 2.7, 3.4 and 3.5[53]
The libgit2 implementation of Git is an ANSI C software library with no other dependencies, which can be built on multiple platforms including Windows, Linux, macOS, and BSD.[54] It has bindings for many programming languages, including Ruby, Python, and Haskell.[55][56][57]
JS-Git is a JavaScript implementation of a subset of Git.[58]
Web interfaces[edit]
Screenshot of Gitweb interface showing a commit diff.
There are various web interfaces available for Git.
Cgit: A web frontend for Git repositories written in C.
Gitweb: A Git frontend written in Perl.
Gogs: A Git frontend with built-in authentication, issue handling, fork and a lot of features, written in Go.
Gitea: A fork of Gogs.
Gitlist: A Git repository viewer using Bootstrap Framework written in PHP.
Git server[edit]
As Git is a distributed version control system, it can be used as a server out of the box. Dedicated Git server software helps, amongst other features, to add access control, display the contents of a Git repository via the web, and help managing multiple repositories. Remote file store and shell access: A Git repository can be cloned to a shared file system, and accessed by other persons. It can also be accessed via remote shell just by having the Git software installed and allowing a user to log in.[59]
See also: Comparison of source code hosting facilities
Adoption[edit]
The Eclipse Foundation reported in its annual community survey that as of May 2014, Git is now the most widely used source-code management tool, with 42.9% of professional software developers reporting that they use Git as their primary source control system[60] compared with 36.3% in 2013, 32% in 2012; or for Git responses excluding use of GitHub: 33.3% in 2014, 30.3% in 2013, 27.6% in 2012 and 12.8% in 2011.[61] Open source directory Black Duck Open Hub reports a similar uptake among open source projects.[62] The Stack Overflow developer survey reported in 2015 that 69.3% of developers use Git; 36.9% use Subversion; 12.2% use TFS; and 7.9% use Mercurial.[63]
The UK IT jobs website itjobswatch.co.uk reports that as of late September 2016, 29.27% of UK permanent software development job openings have cited Git,[64] ahead of 12.17% for Microsoft Team Foundation Server,[65] 10.60% for Subversion,[66] 1.30% for Mercurial,[67] and 0.48% for Visual SourceSafe.[68]
Since February 2017, Microsoft has been in the process of migrating Microsoft Windows development to Git, migrating from Perforce. In order to handle the size of the Windows source code tree, Microsoft was required to develop customizations to the software, including Git Virtual File System (GVFS), a system which allows cloned repositories to use placeholders whose contents are downloaded only once a file is accessed.[69]
Security[edit]
Git does not provide access control mechanisms, but was designed for operation with other tools that specialize in access control.[70]
On 17 December 2014, an exploit was found affecting the Windows and Mac versions of the Git client. An attacker could perform arbitrary code execution on a target computer with Git installed by creating a malicious Git tree (directory) named .git (a directory in Git repositories that stores all the data of the repository) in a different case (such as .GIT or .Git, needed because Git doesn't allow the all-lowercase version of .git to be created manually) with malicious files in the .git/hooks subdirectory (a folder with executable files that Git runs) on a repository that the attacker made or on a repository that the attacker can modify. If a Windows or Mac user pulls (downloads) a version of the repository with the malicious directory, then switches to that directory, the .git directory will be overwritten (due to the case-insensitive trait of the Windows and Mac filesystems) and the malicious executable files in .git/hooks may be run, which results in the attacker's commands being executed. An attacker could also modify the .git/config configuration file, which allows the attacker to create malicious Git aliases (aliases for Git commands or external commands) or modify extant aliases to execute malicious commands when run. The vulnerability was patched in version 2.2.1 of Git, released on 17 December 2014, and announced on the next day.[71][72]
Git version 2.6.1, released on 29 September 2015, contained a patch for a security vulnerability (CVE-2015-7545)[73] which allowed arbitrary code execution.[74] The vulnerability was exploitable if an attacker could convince a victim to clone a specific URL, as the arbitrary commands were embedded in the URL itself.[75] An attacker could use the exploit via a man-in-the-middle attack if the connection was unencrypted,[75] as they could redirect the user to a URL of their choice. Recursive clones were also vulnerable, since they allowed the controller of a repository to specify arbitrary URLs via the gitmodules file.[75]
Git uses SHA-1 hashes internally. Linus Torvalds has responded that the hash was mostly to guard against accidental corruption, and the security a cryptographically secure hash gives was just an accidental side effect, with the main security being signing elsewhere.[76][77]
See also[edit]
Free software portal
Linux portal
Internet portal
GitHub
Comparison of version control software
Comparison of source code hosting facilities
List of revision control software
References[edit]
Jump up ^ "Initial revision of "git", the information manager from hell". Github. 8 April 2005. Archived from the original on 16 November 2015. Retrieved 20 December 2015.
Jump up ^ "Commit Graph". Github. 8 June 2016. Archived from the original on 20 January 2016. Retrieved 19 December 2015.
Jump up ^ "Releases - git/git". Archived from the original on 20 September 2017. Retrieved 2 January 2018.
Jump up ^ "Git Source Code Mirror". Archived from the original on 8 February 2017. Retrieved 1 January 2017.
Jump up ^ "Git's GPL license at github.com". github.com. 18 January 2010. Archived from the original on 11 April 2016. Retrieved 12 October 2014.
Jump up ^ "Git's LGPL license at github.com". github.com. 20 May 2011. Archived from the original on 11 April 2016. Retrieved 12 October 2014.
Jump up ^ "Tech Talk: Linus Torvalds on git (at 00:01:30)". YouTube. Archived from the original on 20 December 2015. Retrieved 20 July 2014.
Jump up ^ Scopatz, Anthony; Huff, Kathryn D. (2015). Effective Computation in Physics. O'Reilly Media, Inc. p. 351. ISBN 9781491901595. Archived from the original on 7 May 2016. Retrieved 20 April 2016.
^ Jump up to: a b Torvalds, Linus (2005-04-07). "Re: Kernel SCM saga." linux-kernel (Mailing list). "So I'm writing some scripts to try to track things a whole lot faster."
^ Jump up to: a b Torvalds, Linus (2007-06-10). "Re: fatal: serious inflate inconsistency". git (Mailing list).
^ Jump up to: a b c d e Linus Torvalds (3 May 2007). Google tech talk: Linus Torvalds on git. Event occurs at 02:30. Archived from the original on 28 May 2007. Retrieved 16 May 2007.
Jump up ^ "A Short History of Git". Pro Git (2nd ed.). Apress. 2014. Archived from the original on 25 December 2015. Retrieved 26 December 2015.
Jump up ^ Chacon, Scott (24 December 2014). Pro Git (2nd ed.). New York, NY: Apress. pp. 29–30. ISBN 978-1-4842-0077-3. Archived from the original on 25 December 2015.
Jump up ^ BitKeeper and Linux: The end of the road? |linux.com Archived 8 June 2017 at the Wayback Machine.
Jump up ^ McAllister, Neil (2 May 2005). "Linus Torvalds' BitKeeper blunder". InfoWorld. IDG. Archived from the original on 26 August 2015. Retrieved 8 September 2015.
Jump up ^ "GitFaq: Why the 'Git' name?". Git.or.cz. Archived from the original on 23 July 2012. Retrieved 14 July 2012.
Jump up ^ "After controversy, Torvalds begins work on 'git'". PC World. 14 July 2012. Archived from the original on 1 February 2011. Torvalds seemed aware that his decision to drop BitKeeper would also be controversial. When asked why he called the new software, "git", British slang meaning "a rotten person", he said. "I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git"
Jump up ^ "git(1) Manual Page". Archived from the original on 21 June 2012. Retrieved 21 July 2012.
Jump up ^ "Initial revision of "git", the information manager from hell · git/git@e83c516". GitHub. Archived from the original on 8 October 2017. Retrieved 21 January 2016.
^ Jump up to: a b Torvalds, Linus (2007-02-27). "Re: Trivia: When did git self-host?". git (Mailing list).
Jump up ^ Torvalds, Linus (2005-04-06). "Kernel SCM saga." linux-kernel (Mailing list).
Jump up ^ Torvalds, Linus (2005-04-17). "First ever real kernel git merge!". git (Mailing list).
Jump up ^ Mackall, Matt (2005-04-29). "Mercurial 0.4b vs git patchbomb benchmark". git (Mailing list).
Jump up ^ Torvalds, Linus (2005-06-17). "Linux 2.6.12". git-commits-head (Mailing list).
Jump up ^ Torvalds, Linus (2005-07-27). "Meet the new maintainer.." git (Mailing list).
Jump up ^ Hamano, Junio C. (2005-12-21). "Announce: Git 1.0.0". git (Mailing list).
Jump up ^ Torvalds, Linus (2006-05-05). "Re: [ANNOUNCE] Git wiki". linux-kernel (Mailing list). "Some historical background" on Git's predecessors
^ Jump up to: a b Torvalds, Linus (2005-04-08). "Re: Kernel SCM saga". linux-kernel (Mailing list). Retrieved 2008-02-20.
^ Jump up to: a b Torvalds, Linus (2006-03-23). "Re: Errors GITtifying GCC and Binutils". git (Mailing list).
Jump up ^ Torvalds, Linus (2006-10-20). "Re: VCS comparison table". git (Mailing list). A discussion of Git vs. BitKeeper
Jump up ^ Git 2.8.0 Release Notes "Documentation/RelNotes/2.8.0.txt". 29 March 2016. Archived from the original on 26 July 2016.
Jump up ^ Torvalds, Linus (2006-10-19). "Re: VCS comparison table". git (Mailing list).
Jump up ^ Jst's Blog on Mozillazine "bzr/hg/git performance". Archived from the original on 29 May 2010. Retrieved 12 February 2015.
Jump up ^ Dreier, Roland (13 November 2006). "Oh what a relief it is". Archived from the original on 16 January 2009. , observing that "git log" is 100x faster than "svn log" because the latter must contact a remote server.
Jump up ^ "Trust". Git Concepts. Git User's Manual. 18 October 2006. Archived from the original on 22 February 2017.
Jump up ^ Torvalds, Linus. "Re: VCS comparison table". git (Mailing list). Retrieved 2009-04-10. , describing Git's script-oriented design
Jump up ^ iabervon (22 December 2005). "Git rocks!". Archived from the original on 14 September 2016. , praising Git's scriptability
Jump up ^ "Git User's Manual". 5 August 2007. Archived from the original on 22 February 2017.
Jump up ^ Torvalds, Linus (2005-04-10). "Re: more git updates." linux-kernel (Mailing list).
Jump up ^ Haible, Bruno (2007-02-11). "how to speed up "git log"?". git (Mailing list).
Jump up ^ Torvalds, Linus (2006-03-01). "Re: impure renames / history tracking". git (Mailing list).
Jump up ^ Hamano, Junio C. (2006-03-24). "Re: Errors GITtifying GCC and Binutils". git (Mailing list).
Jump up ^ Hamano, Junio C. (2006-03-23). "Re: Errors GITtifying GCC and Binutils". git (Mailing list).
Jump up ^ Torvalds, Linus (2006-11-28). "Re: git and bzr". git (Mailing list). , on using git-blame to show code moved between source files
Jump up ^ Torvalds, Linus (18 July 2007). "git-merge(1)". Archived from the original on 16 July 2016.
Jump up ^ Torvalds, Linus (18 July 2007). "CrissCrossMerge". Archived from the original on 13 January 2006.
Jump up ^ Torvalds, Linus (2005-04-10). "Re: more git updates.." linux-kernel (Mailing list).
Jump up ^ "1.4 Getting Started – Installing Git". git-scm.com. Archived from the original on 2 November 2013. Retrieved 1 November 2013.
Jump up ^ Gerrit Code Review – Project Configuration File Format
Jump up ^ "downloads". Archived from the original on 8 May 2012. Retrieved 14 May 2012.
Jump up ^ "msysGit". Archived from the original on 10 October 2016. Retrieved 20 September 2016.
Jump up ^ "JGit". Archived from the original on 31 August 2012. Retrieved 24 August 2012.
Jump up ^ "Dulwich". Archived from the original on 29 May 2012. Retrieved 27 August 2012.
Jump up ^ "libgit2". Archived from the original on 11 April 2016. Retrieved 24 August 2012.
Jump up ^ "rugged". Archived from the original on 24 July 2013. Retrieved 24 August 2012.
Jump up ^ "pygit2". Archived from the original on 5 August 2015. Retrieved 24 August 2012.
Jump up ^ "hlibgit2". Archived from the original on 25 May 2013. Retrieved 30 April 2013.
Jump up ^ "Archived copy". Archived from the original on 7 August 2013. Retrieved 13 August 2013. "js-git: a JavaScript implementation of Git." Retrieved 13 August 2013.
Jump up ^ 4.4 Git on the Server – Setting Up the Server Archived 22 October 2014 at the Wayback Machine., Pro Git.
Jump up ^ "Eclipse Community Survey 2014 results | Ian Skerrett". Ianskerrett.wordpress.com. 23 June 2014. Archived from the original on 25 June 2014. Retrieved 23 June 2014.
Jump up ^ "Results of Eclipse Community Survey 2012". Archived from the original on 11 April 2016.
Jump up ^ "Compare Repositories – Open Hub". Archived from the original on 7 September 2014.
Jump up ^ "Stack Overflow Developer Survey 2015". Stack Overflow. Archived from the original on 11 October 2016. Retrieved 1 October 2016.
Jump up ^ "Git (software) Jobs, Average Salary for Git Distributed Version Control System Skills". Itjobswatch.co.uk. Archived from the original on 8 October 2016. Retrieved 30 September 2016.
Jump up ^ "Team Foundation Server Jobs, Average Salary for Microsoft Team Foundation Server (TFS) Skills". Itjobswatch.co.uk. Archived from the original on 29 October 2016. Retrieved 30 September 2016.
Jump up ^ "Subversion Jobs, Average Salary for Apache Subversion (SVN) Skills". Itjobswatch.co.uk. Archived from the original on 25 October 2016. Retrieved 30 September 2016.
Jump up ^ "Mercurial Jobs, Average Salary for Mercurial Skills". Itjobswatch.co.uk. Archived from the original on 23 September 2016. Retrieved 30 September 2016.
Jump up ^ "VSS/SourceSafe Jobs, Average Salary for Microsoft Visual SourceSafe (VSS) Skills". Itjobswatch.co.uk. Archived from the original on 29 October 2016. Retrieved 30 September 2016.
Jump up ^ "Windows switch to Git almost complete: 8,500 commits and 1,760 builds each day". Ars Technica. Archived from the original on 24 May 2017. Retrieved 24 May 2017.
Jump up ^ "Archived copy". Archived from the original on 14 September 2016. Retrieved 6 September 2016.
Jump up ^ Pettersen, Tim (20 December 2014). "Securing your Git server against CVE-2014-9390". Archived from the original on 24 December 2014. Retrieved 22 December 2014.
Jump up ^ Hamano, J. C. (18 December 2014). "[Announce] Git v2.2.1 (and updates to older maintenance tracks)". Newsgroup: gmane.linux.kernel. Archived from the original on 19 December 2014. Retrieved 22 December 2014.
Jump up ^ "CVE-2015-7545". 15 December 2015. Archived from the original on 26 December 2015. Retrieved 26 December 2015.
Jump up ^ "Git 2.6.1". 29 September 2015. Archived from the original on 11 April 2016. Retrieved 26 December 2015.
^ Jump up to: a b c Blake Burkhart; et al. (5 October 2015). "Re: CVE Request: git". Archived from the original on 27 December 2015. Retrieved 26 December 2015.
Jump up ^ "hash - How safe are signed git tags? Only as safe as SHA-1 or somehow safer?". Information Security Stack Exchange. 22 September 2014. Archived from the original on 24 June 2016.
Jump up ^ "Why does Git use a cryptographic hash function?". Stack Overflow. 1 March 2015. Archived from the original on 1 July 2016.
External links[edit]
Wikimedia Commons has media related to Git.
Wikibooks has a book on the topic of: Git
Official website
Git at Open Hub
[hide]
v
t
e
Version control software
Years, where available, indicate the date of first stable release. Systems with names in italics are no longer maintained or have planned end-of-life dates.
Local only
Free/open-source
RCS (1982)
SCCS (1972)
Proprietary
PVCS (1985)
QVCS (1991)
Client–server
Free/open-source
CVS (1986, 1990 in C)
CVSNT (1998)
QVCS Enterprise (1998)
Subversion (2000)
Proprietary
AccuRev SCM (2002)
ClearCase (1992)
CMVC (1994)
Dimensions CM (1980s)
DSEE (1984)
Endevor (1980s)
Integrity (2001)
Panvalet (1970s)
Perforce Helix (1995)
SCLM (1980s?)
Software Change Manager (1970s)
StarTeam (1995)
Surround SCM (2002)
Synergy (1990)
Team Concert (2008)
Team Foundation Server (2005)
Visual Studio Team Services (2014)
Vault (2003)
Visual SourceSafe (1994)
Distributed
Free/open-source
ArX (2003)
BitKeeper (2000)
Codeville (2005)
Darcs (2002)
DCVS (2002)
Fossil (2007)
Git (2005)
GNU arch (2001)
GNU Bazaar (2005)
Mercurial (2005)
Monotone (2003)
SVK (2003)
Veracity (2010)
Proprietary
TeamWare (1990s?)
Code Co-op (1997)
Plastic SCM (2006)
Team Foundation Server (2013)
Visual Studio Team Services (2014)
Concepts
Branch
Fork
Changeset
Commit
Gated commit
Interleaved deltas
Delta compression
Data comparison
Merge
Repository
Tag
Trunk
Category
Comparison
List
Authority control
GND: 7687494-1
Retrieved from "https://en.wikipedia.org/w/index.php?title=Git&oldid=821910901"
Categories:
2005 software
Concurrent Versions System
Distributed version control systems
Free version control software
Free software programmed in C
Free software programmed in Perl
Git (software)
Linux archivers and compression-related utilities
Self-hosting software
Linus Torvalds
Software using the GPL license
Hidden categories:
Webarchive template wayback links
Use dmy dates from March 2012
Pages using deprecated image syntax
All articles with unsourced statements
Articles with unsourced statements from April 2017
Articles with unsourced statements from February 2017
Wikipedia articles needing clarification from June 2014
Wikipedia articles with GND identifiers
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Wikibooks
Wikiversity
Languages
العربية
Bân-lâm-gú
Български
Bosanski
Català
Čeština
Dansk
Deutsch
Eesti
Ελληνικά
Español
Esperanto
Euskara
فارسی
Français
Galego
ગુજરાતી
한국어
हिन्दी
Hrvatski
Bahasa Indonesia
Italiano
עברית
Қазақша
Latviešu
Magyar
Македонски
മലയാളം
Bahasa Melayu
Nederlands
日本語
Norsk
Polski
Português
Română
Русский
Scots
Simple English
Slovenčina
Slovenščina
Српски / srpski
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Українська
Tiếng Việt
中文
Edit links
This page was last edited on 23 January 2018, at 09:37.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

tag: div

attr: id class

value: mw-page-base noprint

key: html

type: local

value: mw-head-base noprint

tag: a

attr: id class lang

value: firstHeading firstHeading en

value: siteSub noprint

value: jump-to-nav mw-jump

attr: href class title

value:
/wiki/Git_(disambiguation)
mw-disambig
Git (disambiguation)

attr: role class

value:
note
hatnote navigation-not-searchable

tag: caption

tag: img

attr: alt src width height srcset data-file-width data-file-height

attr: href class

tag: td

attr: colspan style

tag: tr

attr: href title

tag: th

attr: scope style

value:
row
white-space: nowrap;

value:
nofollow
external text
https://github.com/git/git

value:
nofollow
external text
https://git-scm.com

value:
/wiki/Version_control_system
mw-redirect
Version control system

value:
/wiki/Source_code_management
mw-redirect
Source code management

value:
/wiki/Distributed_revision_control
mw-redirect
Distributed revision control

value:
/wiki/Source_control_management
mw-redirect
Source control management

value: This claim needs references to reliable sources. (April 2017)

value:
noprint Inline-Template Template-Fact
white-space:nowrap;

value:
background-color: #FDB3AB;
Old version, no longer supported
0.99

value:
background-color: #FDB3AB;
Old version, no longer supported
1.0

value:
background-color: #FDB3AB;
Old version, no longer supported
1.1

value:
background-color: #FDB3AB;
Old version, no longer supported
1.2

value:
background-color: #FDB3AB;
Old version, no longer supported
1.3

value:
background-color: #FDB3AB;
Old version, no longer supported
1.4

value:
background-color: #FDB3AB;
Old version, no longer supported
1.5

value:
background-color: #FDB3AB;
Old version, no longer supported
1.6

value:
background-color: #FDB3AB;
Old version, no longer supported
1.7

value:
background-color: #FDB3AB;
Old version, no longer supported
1.8

value:
background-color: #FDB3AB;
Old version, no longer supported
1.9

value:
background-color: #FDB3AB;
Old version, no longer supported
2.0

value:
background-color: #FDB3AB;
Old version, no longer supported
2.1

value:
background-color: #FDB3AB;
Old version, no longer supported
2.2

value:
background-color: #FDB3AB;
Old version, no longer supported
2.3

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.4

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.5

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.6

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.7

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.8

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.9

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.10

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.11

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.12

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.13

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.14

value:
templateVersion co
background-color: #FEF8C6;
Older version, yet still supported
2.15

value:
templateVersion c
background-color: #D4F4B4;
Current stable version
2.16

value: border-left: 1.2em solid #FDB3AB; padding-left: 0.3em; white-space: nowrap;

value: border-left: 1.2em solid #FEF8C6; padding-left: 0.3em; white-space: nowrap;

value: border-left: 1.2em solid #D4F4B4; padding-left: 0.3em; white-space: nowrap;

value: border-left: 1.2em solid #FED1A0; padding-left: 0.3em; white-space: nowrap;

value: border-left: 1.2em solid #C1E6F5; padding-left: 0.3em; white-space: nowrap;

value: float: left; margin-left: 1em; display: none;

value: the content is highly questionable and hence proper citation is required (February 2017)

value:
/wiki/Bazaar_(software)
mw-redirect
Bazaar (software)

value:
/wiki/Three-way_merge
mw-redirect
Three-way merge

attr: alt src width height class srcset data-file-width data-file-height

value:
/wiki/Merkle_Tree
mw-redirect
Merkle Tree

value:
/wiki/TCP_and_UDP_port
mw-redirect
TCP and UDP port

value: The text near this tag may need clarification or removal of jargon. (June 2014)

value:
noprint Inline-Template
margin-left:0.1em; white-space:nowrap;

value:
nofollow
https://git.zx2c4.com/cgit/
external text

value: Comparison of source code hosting facilities

value:
/wiki/Black_Duck_Open_Hub
mw-redirect
Black Duck Open Hub

value:
/wiki/Visual_SourceSafe
mw-redirect
Visual SourceSafe

value:
/wiki/Portal:Free_software
mw-redirect
Portal:Free software

value: display:table-cell;padding:0.2em 0.2em 0.2em 0.3em;vertical-align:middle

value: margin:0.5em 0 0.5em 1em;border:solid #aaa 1px

value:
/wiki/List_of_revision_control_software
mw-redirect
List of revision control software

value:
nofollow
external text
https://github.com/git/git/releases

value:
nofollow
external text
https://git-scm.com/book/en/v2

value:
nofollow
external text
https://git-scm.com/docs/git.html

value:
nofollow
https://lwn.net/Articles/165202/
external text

value:
nofollow
external text
http://revctrl.org/CrissCrossMerge

value:
nofollow
external text
https://git-scm.com/downloads

value:
nofollow
external text
https://github.com/msysgit/msysgit

value:
nofollow
https://www.eclipse.org/jgit/
external text

value:
nofollow
https://www.samba.org/~jelmer/dulwich/
external text

value:
nofollow
external text
https://github.com/libgit2/rugged

value:
nofollow
external text
https://github.com/libgit2/pygit2

value:
nofollow
external text
https://github.com/creationix/js-git

value:
nofollow
external text
news:gmane.linux.kernel

value:
nofollow
external text
http://seclists.org/oss-sec/2015/q4/67

value: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

value:
nofollow
external text
https://www.openhub.net/p/git

value: Revision controlled project visualization-2010-24-02.svg

value:
navbox-image
4
width:1px;padding:0px 0px 0px 2px

value: IBM Configuration Management Version Control (CMVC)

value:
/wiki/Perforce_Helix
mw-redirect
Perforce Helix

value: IBM Software Configuration and Library Manager

value:
/wiki/Visual_Studio_Team_Services
mw-redirect
Visual Studio Team Services

value:
/wiki/Data_comparison
mw-redirect
Data comparison

value: nowraplinks hlist collapsible autocollapse navbox-inner

value:
nofollow
external text
https://d-nb.info/gnd/7687494-1

value: Category:Distributed version control systems

value: Category:Free software programmed in Perl

value: Category:Linux archivers and compression-related utilities

value: Category:Webarchive template wayback links

value: Category:Pages using deprecated image syntax

value: Category:All articles with unsourced statements

value: Category:Articles with unsourced statements from April 2017

value: Category:Articles with unsourced statements from February 2017

value: Category:Wikipedia articles needing clarification from June 2014

value: Category:Wikipedia articles with GND identifiers

value: Discussion about edits from this IP address [ctrl-alt-n]

value: A list of edits made from this IP address [ctrl-alt-y]

value:
/wiki/Git
View the content page [ctrl-alt-c]
c

value:
/w/index.php?title=Git&action=edit
Edit this page [ctrl-alt-e]
e

value: About the project, what you can do, where to find things

value: A list of recent changes in the wiki [ctrl-alt-r]

value: portal navigation p-interaction p-interaction-label

value: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

value: Recent changes in pages linked from this page [ctrl-alt-k]

value:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

value: A list of all special pages [ctrl-alt-q]

value: Permanent link to this revision of the page

value: Link to connected data repository item [ctrl-alt-g]

value: Printable version of this page [ctrl-alt-p]

value: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

value:
uls-settings-trigger
Language settings
0
button
true

value: جت (برنامج) – Arabic

value:
https://ca.wikipedia.org/wiki/Git
Git – Catalan
ca
ca
interlanguage-link-target

value:
https://cs.wikipedia.org/wiki/Git
Git – Czech
cs
cs
interlanguage-link-target

value:
https://da.wikipedia.org/wiki/Git
Git – Danish
da
da
interlanguage-link-target

value:
https://de.wikipedia.org/wiki/Git
Git – German
de
de
interlanguage-link-target

value:
https://et.wikipedia.org/wiki/Git
Git – Estonian
et
et
interlanguage-link-target

value: Git (λογισμικό) – Greek

value:
https://es.wikipedia.org/wiki/Git
Git – Spanish
es
es
interlanguage-link-target

value:
https://eo.wikipedia.org/wiki/Git
Git – Esperanto
eo
eo
interlanguage-link-target

value:
https://eu.wikipedia.org/wiki/Git
Git – Basque
eu
eu
interlanguage-link-target

value: گیت (نرم‌افزار) – Persian

value:
https://fr.wikipedia.org/wiki/Git
Git – French
fr
fr
interlanguage-link-target

value:
https://gl.wikipedia.org/wiki/Git
Git – Galician
gl
gl
interlanguage-link-target

value: ગીટ (સોફ્ટવેર) – Gujarati

value:
https://hr.wikipedia.org/wiki/Git
Git – Croatian
hr
hr
interlanguage-link-target

value:
https://id.wikipedia.org/wiki/Git
Git – Indonesian
id
id
interlanguage-link-target

value:
https://kk.wikipedia.org/wiki/Git
Git – Kazakh
kk
kk
interlanguage-link-target

value:
https://lv.wikipedia.org/wiki/Git
Git – Latvian
lv
lv
interlanguage-link-target

value:
https://hu.wikipedia.org/wiki/Git
Git – Hungarian
hu
hu
interlanguage-link-target

value:
https://mk.wikipedia.org/wiki/Git
Git – Macedonian
mk
mk
interlanguage-link-target

value:
https://ms.wikipedia.org/wiki/Git
Git – Malay
ms
ms
interlanguage-link-target

value:
https://ja.wikipedia.org/wiki/Git
Git – Japanese
ja
ja
interlanguage-link-target

value:
https://no.wikipedia.org/wiki/Git
Git – Norwegian
no
no
interlanguage-link-target

value:
https://pt.wikipedia.org/wiki/Git
Git – Portuguese
pt
pt
interlanguage-link-target

value:
https://ro.wikipedia.org/wiki/Git
Git – Romanian
ro
ro
interlanguage-link-target

value:
https://ru.wikipedia.org/wiki/Git
Git – Russian
ru
ru
interlanguage-link-target

value:
https://sco.wikipedia.org/wiki/Git
Git – Scots
sco
sco
interlanguage-link-target

value:
https://sl.wikipedia.org/wiki/Git
Git – Slovenian
sl
sl
interlanguage-link-target

value: Гит (софтвер) – Serbian

value:
https://fi.wikipedia.org/wiki/Git
Git – Finnish
fi
fi
interlanguage-link-target

value:
https://sv.wikipedia.org/wiki/Git
Git – Swedish
sv
sv
interlanguage-link-target

value: கிட் (மென்பொருள்) – Tamil

value: กิต (ซอฟต์แวร์) – Thai

value:
https://uk.wikipedia.org/wiki/Git
Git – Ukrainian
uk
uk
interlanguage-link-target

value:
https://zh.wikipedia.org/wiki/Git
Git – Chinese
zh
zh
interlanguage-link-target

value: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

value: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

value:
suggestions
display: none; font-size: 13px;

value: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Git rootpage-Git skin-vector action-view