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

Re: [PATCH QGit RFC] Fix "Save patch..." on a commit range

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Jun 13, 2009, 07:13 UTC
Message-ID
<e5bfff550906130013j3a9802cen48ac5828a2357bf1@mail.gmail.com>
In-Reply-To
<1244849357-31166-1-git-send-email-markus.heidelberg@web.de>

On Sat, Jun 13, 2009 at 00:29, Markus Heidelberg<markus.heidelberg@web.de> wrote:

Show 5 quoted lines
> Creating a patch series didn't work, because the SHA1 list was
> interpreted in the wrong order.
>
> Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
> ---
I think they are generated in apply order as should be.
As example, from git repo we have the following revisions:

GIT 1.6.3 t4029: use sh instead of bash t4200: convert sed expression which operates on non-text file to perl t4200: remove two unnecessary lines

Now if I select the 4 revisions and use "Save patch..." I have

0001-t4200-remove-two-unnecessary-lines.patch 0002-t4200-convert-sed-expression-which-operates-on-non.patch 0003-t4029-use-sh-instead-of-bash.patch 0004-GIT-1.6.3.patch

That is correct because if I go to apply the patches I have to apply in the reverse cronological order, from the oldest to the newest.

Previous: Markus HeidelbergNext: Markus Heidelberg
Message 2 of 15 in “Fix "Save patch..." on a commit range”
  1. Fix "Save patch..." on a commit rangeMarkus Heidelberg, Jun 12, 2009
  2. Marco CostalbaJun 13, 2009
  3. Markus HeidelbergJun 13, 2009
  4. Markus HeidelbergJun 13, 2009
  5. Marco CostalbaJun 13, 2009
  6. Markus HeidelbergJun 13, 2009
  7. Marco CostalbaJun 13, 2009
  8. Markus HeidelbergJun 15, 2009
  9. Marco CostalbaJun 15, 2009
  10. Marco CostalbaJun 15, 2009
  11. Marco CostalbaJun 15, 2009
  12. Markus HeidelbergJun 15, 2009
  13. Marco CostalbaJun 16, 2009
  14. Markus HeidelbergJun 16, 2009
  15. Markus HeidelbergJun 15, 2009

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.