Re: [PATCH v2 04/15] user-manual: Use git branch --merged

From: W. Trevor King <wking@tremily.us>
Date: Feb 10, 2013, 21:56 UTC
Message-ID: <20130210215631.GC8000@odin.tremily.us>
In-Reply-To: <7v4nhju9z6.fsf@alter.siamese.dyndns.org>

On Sun, Feb 10, 2013 at 01:37:01PM -0800, Junio C Hamano wrote:

Show 6 quoted lines

> This is making things much less useful.  "branch --merged origin"
> will show 47 different branches that you are *not* interested in the
> flow of examples in this part of the tutorial.
> 
> Also, log origin..branchname allows you to notice a situation where
> some but not all of the branch was merged, too.

Good points.  I'll drop this patch from v3.

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

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