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

Re: [PATCH 0/2] Setting git tree of a patch (improved version)

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
May 25, 2010, 12:26 UTC
Message-ID
<AANLkTimgpjn5KZpujtmXfd7UtEfJTg-3UcmIjvFor0bX@mail.gmail.com>
In-Reply-To
<20100524184908.30884.65042.stgit@sambuntu>
On 24 May 2010 19:52, Gustav Hållberg <gustav@gmail.com> wrote:
Show 8 quoted lines
> I solved (I think) how to accept (and verify the correctness of) a
> tree-ish as argument for 'edit --set-tree'. The first patch in the
> series adds support to Repository.rev_parse() for doing that.
>
> The main (the second) is essentially the same as before.
>
> I moved the --set-tree option to be last in the list of options,
> making it even more obscure-looking.
The patches look fine to me.

Do you want me to merge them directly or I grab them via some git tree (or Karl's).

Thanks.
-- 
Catalin
Previous: Gustav HållbergNext: Gustav Hållberg
Message 14 of 16 in “edit: Allow setting git tree SHA1 of a patch”
  1. edit: Allow setting git tree SHA1 of a patchGustav Hållberg, May 16, 2010
  2. Karl WibergMay 17, 2010
  3. Catalin MarinasMay 21, 2010
  4. David KågedalMay 21, 2010
  5. Catalin MarinasMay 21, 2010
  6. David KågedalMay 21, 2010
  7. Gustav HållbergMay 21, 2010
  8. Catalin MarinasMay 21, 2010
  9. David KågedalMay 21, 2010
  10. Gustav HållbergMay 21, 2010
  11. 0/2 Setting git tree of a patch (improved version)Gustav Hållberg, May 24, 2010
  12. 1/2 Repository.rev_parse: support commits, trees, and blobsGustav Hållberg, May 24, 2010
  13. 2/2 edit: Allow setting git tree of a patchGustav Hållberg, May 24, 2010
  14. Catalin MarinasMay 25, 2010
  15. Gustav HållbergMay 26, 2010
  16. Catalin MarinasMay 26, 2010

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.