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

Re: git pull with "no common commits" : danger?

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Apr 8, 2010, 02:08 UTC
Message-ID
<4BBD3A98.2020207@drmicha.warpmail.net>
In-Reply-To
<v2t3abd05a91004071856s5811e086q17241996a359e172@mail.gmail.com>
Aghiles venit, vidit, dixit 08.04.2010 09:56:
Show 6 quoted lines
> Hello,
> 
> I mistakenly pulled a project into another project. I had the
> "warning: no common commits" but the pull did proceed.
> I am wondering if, from a usability point of view, it would be
> best to avoid doing so by default.
Puleeezze: No animals were harmed during the process, right? I mean, no
data loss, all you have to do is a git reset. Let's try and not make Git
into "Are you sure"dom.
Michael
Previous: AghilesNext: Aghiles
Message 2 of 7 in “git pull with "no common commits" : danger?”
  1. AghilesApr 8, 2010
  2. Michael J GruberApr 8, 2010
  3. AghilesApr 8, 2010
  4. Jonathan NiederApr 8, 2010
  5. AghilesApr 8, 2010
  6. Junio C HamanoApr 8, 2010
  7. AghilesApr 8, 2010

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.