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

Re: [RFC] Patches exchange is bad?

From
MCMarco Costalba <mcostalba@yahoo.it>
Date
Aug 16, 2005, 22:09 UTC
Message-ID
<20050816220923.42545.qmail@web26301.mail.ukl.yahoo.com>
Martin Langhoff wrote:
Show 5 quoted lines
>>From what I understand, you'll want the StGIT infrastructure. If you
>use git/cogito, there is an underlying  assumption that you'll want
>all the patches merged across, and a simple cg-update will bring in
>all the pending stuff.
>
My concerns are both metodologicals and practical:
1) Method: To use the 'free patching workflow' on git is something foreseen in
git design, something coherent with the fork + develop + merge cycle that it
seems, at least to me, THE way git is meant to be used. Or it is stretching 
the possibility of the tool to something technically allowed but not suggested.
2) Practical: The round trip git-format-patch + git-applymbox is the logical and
natural way to reach this goal or, also in this case, I intend to stretch some tools, 
designed for one thing, for something else?

About StGIT, I agree it is the right tool, designed for this kind of problems. But, peraphs because I don't know it very much, I still can't figure out how to integrate StGit in a git GUI, like qgit is, so to have an unified and friendly view of a git archive and a patches stack.

Marco

__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Next: Daniel Barkalow
Message 1 of 2 in “Re: [RFC] Patches exchange is bad?”
  1. Marco CostalbaAug 16, 2005
  2. Daniel BarkalowAug 16, 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.