Re: [PATCH] git-seek: Eliminate spurious warning. Fix errant reference to git-bisect in docs.

From: Junio C Hamano <junkio@cox.net>
Date: Feb 24, 2006, 06:02 UTC
Message-ID: <7vslq9fg53.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <87vev5r2m4.wl%cworth@cworth.org>

Carl Worth <cworth@cworth.org> writes:

Show 8 quoted lines

>> I wonder if its a good idea to silently reset a branch named with a
>> short common word?
>
> It at least takes some care not to leave commits dangling when doing
> this, (the seek branch must at least be a subset of the current
> HEAD). I was pretty much following the lead of git-bisect here,
> (though "bisect" is definitely a touch longer and less common than
> "seek").

IIUC Cogito seems to use cg-seek-point or something long and unusual like that...

$ 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.