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

Re: [PATCH] Add --patchdepth parameter to git-am.sh

From
Junio C Hamano <junkio@cox.net>
Date
Feb 7, 2007, 08:27 UTC
Message-ID
<7vfy9ibcdx.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200702051924.39205.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> writes:
Show 11 quoted lines
> If the series of patches you are applying via git-am was based in a
> different directory there was no way to strip the directory (as you
> would with git-apply).
>
> This patch adds a --patchdepth option to git-am.sh whose argument is
> passed as a "-p" option to git-apply.
>
> Signed-off-by: Andy Parkins <andyparkins@gmail.com>
> ---
> I know git-apply isn't going anywhere, but git-applypatch is.  However, all
> this talk of it made me remember this patch.

I do not understand this remark, as applypatch does not have -p either. If we were to do this, I agree with others that this should simply be called -p (we do not have name crash with existing options, do we?).

I am not sure how useful applying a patch though git-am with -p would be. I can understand,

After seeing that a patch does not apply because the patch was generated at the wrong level, it would be very natural to use "git apply -p0 --index .dotest/patch" and then continue with "git am --resolved". So obviously, -p to git-apply is very useful, but -p given to "am" means all of the patches in your mailbox has uniformly wrong patch depth. I wonder how common would that be in practice.

But other than that "how useful would that be in practice?" issue, I do not think the patch is too bad, except one hunk:

Show 8 quoted lines
> @@ -389,12 +392,12 @@ do
>  	fi
>  
>  	echo
> -	echo "Applying '$SUBJECT'"
> +	echo "Applying '$SUBJECT' at depth $patchdepth"
>  	echo
>  
This is wrong if you do not use any $patchdepth.
Previous: Shawn O. PearceNext: Jakub Narebski
Message 25 of 36 in “Deprecation/Removal schedule”
  1. Junio C HamanoFeb 5, 2007
  2. Shawn O. PearceFeb 5, 2007
  3. Jakub NarebskiFeb 5, 2007
  4. Jakub NarebskiFeb 5, 2007
  5. Shawn O. PearceFeb 5, 2007
  6. Alex RiesenFeb 5, 2007
  7. Shawn O. PearceFeb 5, 2007
  8. Alex RiesenFeb 5, 2007
  9. Shawn O. PearceFeb 5, 2007
  10. Alex RiesenFeb 6, 2007
  11. Johannes SchindelinFeb 6, 2007
  12. Jeff KingFeb 6, 2007
  13. Johannes SchindelinFeb 6, 2007
  14. Alex RiesenFeb 6, 2007
  15. Johannes SchindelinFeb 6, 2007
  16. Alex RiesenFeb 6, 2007
  17. Alex RiesenFeb 6, 2007
  18. Mark WoodingFeb 5, 2007
  19. Johannes SchindelinFeb 5, 2007
  20. Alex RiesenFeb 5, 2007
  21. Linus TorvaldsFeb 5, 2007
  22. Junio C HamanoFeb 5, 2007
  23. Add --patchdepth parameter to git-am.shAndy Parkins, Feb 5, 2007
  24. Shawn O. PearceFeb 5, 2007
  25. Junio C HamanoFeb 7, 2007
  26. Jakub NarebskiFeb 7, 2007
  27. Andy ParkinsFeb 7, 2007
  28. Andreas EricssonFeb 6, 2007
  29. Alex RiesenFeb 6, 2007
  30. Johannes SchindelinFeb 6, 2007
  31. Junio C HamanoFeb 7, 2007
  32. Jakub NarebskiFeb 7, 2007
  33. Johannes SchindelinFeb 7, 2007
  34. Jakub NarebskiFeb 7, 2007
  35. Junio C HamanoFeb 7, 2007
  36. Johannes SchindelinFeb 7, 2007

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.