all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: 70847@debbugs.gnu.org
Subject: bug#70847: 29.3; eshell scripts "from anywhere"
Date: Fri, 24 May 2024 19:17:54 -0700	[thread overview]
Message-ID: <5fd38ab9-22ce-61ea-ba95-b9375a8b6083@gmail.com> (raw)
In-Reply-To: <87pltbwahm.fsf@librehacker.com>

On 5/24/2024 7:27 AM, Christopher Howard wrote:
> Hi, I'm having trouble applying some of these patches to the 29.3 source code I have through guix
> 
> ```
> error: patch failed: lisp/eshell/esh-module.el:49
> error: lisp/eshell/esh-module.el: patch does not apply
> error: patch failed: test/lisp/eshell/eshell-tests-helpers.el:63
> error: test/lisp/eshell/eshell-tests-helpers.el: patch does not apply
> error: test/lisp/eshell/eshell-tests-unload.el: No such file or directory
> ```
> 
> Could you please provide the git url and commit hash that you are patching?

Anything from a relatively recent commit on the master branch should be 
plenty (though the parent commit for my branch is 
eedb959441578f9b4e62b78e1a772328bffe9466). You should be able to get the 
repo from Savannah: <https://git.savannah.gnu.org/git/emacs.git>.





  reply	other threads:[~2024-05-25  2:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 17:57 bug#70847: 29.3; eshell scripts "from anywhere" Christopher Howard
2024-05-23 20:30 ` Jim Porter
2024-05-24 14:27 ` Christopher Howard
2024-05-25  2:17   ` Jim Porter [this message]
2024-05-28 19:42 ` Christopher Howard
2024-05-28 21:51   ` Jim Porter
2024-05-28 19:46 ` Christopher Howard
2024-05-28 22:49 ` Christopher Howard
2024-05-29  0:31   ` Jim Porter
2024-05-29 14:16 ` Christopher Howard
2024-05-29 19:22   ` Jim Porter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5fd38ab9-22ce-61ea-ba95-b9375a8b6083@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=70847@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.