From: zimoun <zimon.toutoune@gmail.com>
To: luis.felipe.la@protonmail.com, 39635@debbugs.gnu.org
Cc: sirgazil@zoho.com, maxim.cournoyer@gmail.com
Subject: [bug#39635] [PATCH] website: Modify use of H1 headings
Date: Mon, 12 Oct 2020 10:02:23 +0200 [thread overview]
Message-ID: <CAJ3okZ1AxA31UMKJc5LhVEU2+Gj8RZ5Q9HUVdvfhLV2XA9KB_A@mail.gmail.com> (raw)
In-Reply-To: <Ye8Qtu3z3EJLQkPYTko-BBX7xEEqR9sL9a6Blwe7HQFgLe2jc1973WZzO7WnfovRVLt9Oky1wdss6YmT-YcaGytjgN8uRlVD7bStoRf10is=@protonmail.com>
Dear,
On Sat, 10 Oct 2020 at 21:58, Luis Felipe via Guix-patches via
<guix-patches@gnu.org> wrote:
> Well, that's unfortunate because that patch is all I have. The copy of the git repository I was working on is long gone.
Sad!
Since I have hit this issue several times when digging in the
Bug/Patch Report, now when sending patches, I personally try to use:
git format-patch --base <commit-where-it-applies>
Then the patch contains at the bottom these lines, for example:
--8<---------------cut here---------------start------------->8---
base-commit: 679d5e6b3dcac4ee1f419c04b3719fead0bd9ee5
--
2.28.0
--8<---------------cut here---------------end--------------->8---
And with a recent enough Magit version, it is "W c C-m b".
Well, it seems a good habit iMHO and I will try to send a patch
updating the section "Submitting Patches".
Thanks,
simon
next prev parent reply other threads:[~2020-10-12 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 18:26 [bug#39635] [PATCH] website: Modify use of H1 headings sirgazil via Guix-patches via
2020-10-06 14:03 ` [bug#39635] " Luis Felipe via Guix-patches via
2020-10-09 2:49 ` [bug#39635] [PATCH] " Maxim Cournoyer
2020-10-10 19:51 ` Luis Felipe via Guix-patches via
2020-10-12 8:02 ` zimoun [this message]
2020-10-12 14:08 ` Luis Felipe via Guix-patches via
2020-10-13 1:36 ` Maxim Cournoyer
2022-10-18 15:58 ` zimoun
2022-10-18 21:34 ` Luis Felipe via Guix-patches via
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=CAJ3okZ1AxA31UMKJc5LhVEU2+Gj8RZ5Q9HUVdvfhLV2XA9KB_A@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=39635@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=sirgazil@zoho.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).