git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Using git clone

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Nov 8, 2014, 17:15 UTC
Message-ID
<20141108171539.GB162918@vauxhall.crustytoothpaste.net>
In-Reply-To
<1415120399.4259.5.camel@precision690.xccg.com>
On Tue, Nov 04, 2014 at 11:59:59AM -0500, Dr. George E. Moore wrote:
> Is it appropriate to use "git clone" to update the master branch of an
> existing repository? The current master branch is for a much earlier
> release candidate.

You generally want to use git fetch or git pull in that case. git clone creates an entirely new copy of the original repository.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: Dr. George E. MooreNext: Matthieu Moy
Message 2 of 3 in “Using git clone”
  1. Dr. George E. MooreNov 4, 2014
  2. brian m. carlsonNov 8, 2014
  3. Matthieu MoyNov 9, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.