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

Re: new file leaked onto release branch

From
Tom Prince <tom.prince@ualberta.net>
Date
Dec 14, 2005, 21:26 UTC
Message-ID
<20051214212612.GA24501@socrates>
In-Reply-To
<7virtrxv9c.fsf@assigned-by-dhcp.cox.net>
On Wed, Dec 14, 2005 at 12:45:51PM -0800, Junio C Hamano wrote:
Show 6 quoted lines
> 
> I pointed out one anomaly which is the commit should never have
> been created because it was not even a fast forward but already
> up-to-date case, and it was followed up with exchange of a few
> messages between Linus and you.
>

I don't remember any of the details now, but I remember that an old version of git or cogito would create bogus fast-forward merges, if they were used without GNU coreutils. The machine it happend on was running FreeBSD 4.10, but current versions work fine.

  Tom
Previous: Junio C Hamano
Message 5 of 5 in “RE: new file leaked onto release branch”
  1. Brown, LenDec 14, 2005
  2. Linus TorvaldsDec 14, 2005
  3. Junio C HamanoDec 18, 2005
  4. Junio C HamanoDec 14, 2005
  5. Tom PrinceDec 14, 2005

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.