unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Exporting patches without prerequisite patch id
Date: Wed, 03 Aug 2022 20:22:02 -0400	[thread overview]
Message-ID: <87czdgq2mt.fsf@kyleam.com> (raw)
In-Reply-To: <20220803035700.5fecda10@aria>

kiasoc5 writes:

> I have some commits on my local guix repo like this:
>
> (master) HEAD -> A -> B -> C
>
> When I do `git format-patch -3 --base=auto` I get prerequisite patch
> ids in some of the patches. But I want to each patch to depend only on
> HEAD. In other words I want to export patches like so:
>
> HEAD -> A
> HEAD -> B
> HEAD -> C
>
> How do I do this?

`git-format-patch --base` doesn't support lying about the state by
leaving out the prerequisite patch IDs, as far as I know.  If you have a
string of commits that you want to post as single patches where only
base-commit is listed, the approach would be to split each of those off
into separate, independent branches on top of the base commit.

             a
            /
    base ----- b
            \
             c


      reply	other threads:[~2022-08-04  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  3:57 Exporting patches without prerequisite patch id kiasoc5
2022-08-04  0:22 ` Kyle Meyer [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87czdgq2mt.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=help-guix@gnu.org \
    --cc=kiasoc5@disroot.org \
    /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).