Re: [ANNOUNCE] pg - A patch porcelain for GIT

From: Shawn Pearce <spearce@spearce.org>
Date: Feb 10, 2006, 21:04 UTC
Message-ID: <20060210210401.GA1604@spearce.org>
In-Reply-To: <20060210204143.GA18784@kroah.com>

Greg KH <greg@kroah.com> wrote:

Show 7 quoted lines

> On Fri, Feb 10, 2006 at 02:59:14PM -0500, Shawn Pearce wrote:
> > I just posted the first public version of pg, a GIT porcelain for
> > managing patches.  Think StGIT, but better in some ways:
> > 
> > Feature Summary:
> 
> Hm, is there any way to import an existing patch into pg?

Doh! I haven't needed to do that yet. I'll code up a pg-import later tonight. But since git and pg play nice together you can do this:

	pg-new Patch-Name
	git-apply the-patch-file.patch
	pg-ci -m"Importing the-patch-file.patch..."

or even:

	pg-new Patch-Name
	git-am mbox

and keep the 'history' stored in the mailbox.

So pg-import won't amount to a very long script.  :-|

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