all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Benjamin Orthen <benjamin@orthen.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 62093@debbugs.gnu.org
Subject: bug#62093: 30.0.50; tramp: commit 8c6a463 breaks remotely staging chunks in magit
Date: Tue, 04 Apr 2023 09:13:06 +0000	[thread overview]
Message-ID: <9d83b61ae2e3f563428ef7290a614d60@orthen.net> (raw)
In-Reply-To: <87cz4wivgf.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

Hi Michael,

sure. You'll need a git repository on a remote host with unstaged 
changes.

In the git repository, execute:
- `magit-status`
- `magit-jump-to-unstaged`
- navigate the cursor to one unstaged chunk in the diff (see attached 
image as an example)
- `magit-stage`

I hope this helps for reproducing the issue.

Best,
Benjamin


Am 2023-03-25 17:37, schrieb Michael Albinus:
> Benjamin Orthen <benjamin@orthen.net> writes:
> 
> Hi Benjamin,
> 
>> To reproduce:
>> - use tramp to visit a remote Linux host
>> - open magit on a git repository on the remote host
>> - in the magit buffer, try to stage a chunk (not a whole file)
> 
> I'm sorry, but I don't use magit myself. Could you please describe the
> magit commands I have to apply in Emacs in order to reproduce?
> 
> Best regards, Michael.

[-- Attachment #2: Screenshot from 2023-04-04 11-08-54.png --]
[-- Type: image/png, Size: 25158 bytes --]

  reply	other threads:[~2023-04-04  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 10:42 bug#62093: 30.0.50; tramp: commit 8c6a463 breaks remotely staging chunks in magit Benjamin Orthen
2023-03-25 17:37 ` Michael Albinus
2023-04-04  9:13   ` Benjamin Orthen [this message]
2023-06-02  4:18 ` bug#62093: 30.0.50; tramp: commit 8c6a463 breaks remotely Marc Bowes

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=9d83b61ae2e3f563428ef7290a614d60@orthen.net \
    --to=benjamin@orthen.net \
    --cc=62093@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.