public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: [PATCH] gas: Fix some typos in the Info manual
Date: Tue, 09 Aug 2022 23:36:06 +0200	[thread overview]
Message-ID: <20220809233606+0200.140642-stepnem@gmail.com> (raw)
In-Reply-To: <3e1db456-5247-9ad4-0ed1-656558af3844@redhat.com>

Hello Nick,

On Tue, 09 Aug 2022 16:33:49 +0100
Nick Clifton wrote:

> If I have understood correctly, I have to save the entire email to a
> file, and then run "git am <file>" to have the patch applied.

Yes, that's one way. Many people use some kind of MUA or text editor
integration or scripts, e.g., pipe the message to a command (like
git-am(1)) directly without an explicit saving middle step.

> But this automatically commits the patch, even if I do not want to do
> so. So then if I decide that the patch is wrong in some way I have to
> revert the commit and reset the sources. But if I like the commit I
> can push it straight away. Right ?

If you wish to only apply the patch changes without committing you could
use git-apply(1) instead of git-am(1), though it might be more
convenient to commit the patch first anyway (git am), check or test it
and if you want to change something in-place, you can just make the
changes and use `git commit --amend` to modify that last commit (HEAD)
before pushing.

  Thanks,

  Štěpán

      reply	other threads:[~2022-08-09 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 17:38 Štěpán Němec
2022-08-09 14:39 ` Nick Clifton
2022-08-09 15:06   ` Štěpán Němec
2022-08-09 15:33     ` Nick Clifton
2022-08-09 21:36       ` Štěpán Němec [this message]

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=20220809233606+0200.140642-stepnem@gmail.com \
    --to=stepnem@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).