all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: jgart <jgart@dismail.de>
Cc: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: Patch Review Flow
Date: Tue, 7 Nov 2023 14:38:51 +0200	[thread overview]
Message-ID: <ZUov26Xl4yj6Ezx5@3900XT> (raw)
In-Reply-To: <6ce5749cf43f9c39a77f0635b512d306@dismail.de>

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

On Tue, Nov 07, 2023 at 12:32:35PM +0000, jgart wrote:
> Hi Efraim,
> 
> Thanks for sharing your approach as well. IIRC, a user can't interactively cherry-pick a range with tig. If you find a way please do share ;()

It looks like 'C' (that's a 'big c') over a commit will offer to
cherry-pick the commit.  Alternatively, if you're still looking at the
branches then 'C' will offer to checkout that branch.

Tig asks for an explicit y or n, so pressing enter for the prompt won't
do anything.

I should probably look at the different options tig has. I've had it
installed forever but only ever used it for viewing commits and
branches.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-11-07 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 21:25 Patch Review Flow jgart
2023-11-06  7:51 ` Christopher Baines
2023-11-06 13:51   ` Clément Lassieur
2023-11-07  8:56   ` Efraim Flashner
2023-11-07 12:32   ` jgart
2023-11-07 12:38     ` Efraim Flashner [this message]
2023-11-07 16:29     ` jgart
2023-11-06 14:49 ` jgart
2023-11-07 17:24 ` Maxim Cournoyer
2023-11-07 20:09 ` jgart
2023-12-10 12:47   ` Tobias Alexandra Platen

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=ZUov26Xl4yj6Ezx5@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=mail@cbaines.net \
    /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/guix.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.