all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@posteo.net>
To: Tobias Geerinckx-Rice <somebody@not-sent-or-endorsed-by.tobias.gr>
Cc: 33338@debbugs.gnu.org
Subject: [bug#33338] [PATCH] gnu: Add emacs-webpaste
Date: Sun, 25 Nov 2018 09:52:19 -0600	[thread overview]
Message-ID: <875zwlgnnw.fsf@posteo.net> (raw)
In-Reply-To: <87d0qtv5az.fsf@nckx>


Tobias Geerinckx-Rice writes:

> Brett,
>
> Brett Gilio wrote:
>> When I run git format-patch -1 I suppose it isn't adding the commit
>> log
>> to the patch file? I think that is what you are trying to say. How
>> then
>> should I add it, because I am making commits before I generate the
>> patch?
>
> That's the normal (only?) way. ‘git format-patch’es will include
> whatever commit messages you wrote during ’git commit’, and which are
> displayed by ’git log’, ‘git show’, et al.
>
> What do the latter commands show?
>
> Kind regards,
>
> T G-R

The patches are including the commit in the name of the format itself,
but it seems like ludo is wanting something contained within the patch
itself which it is not doing.

Git log is showing my commit history with the messages, git show is
also. So, I am confused as to what exactly I am not doing correctly.

Brett

  reply	other threads:[~2018-11-25 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-10 21:04 [bug#33338] [PATCH] gnu: Add emacs-webpaste Brett Gilio
     [not found] ` <handler.33338.B.154188391713669.ack@debbugs.gnu.org>
2018-11-10 21:08   ` [bug#33338] Acknowledgement ([PATCH] gnu: Add emacs-webpaste) Brett Gilio
2018-11-19 21:36 ` [bug#33338] [PATCH] gnu: Add emacs-webpaste Ludovic Courtès
2018-11-24 21:02   ` Brett Gilio
2018-11-25 10:07     ` Tobias Geerinckx-Rice
2018-11-25 15:52       ` Brett Gilio [this message]
2018-11-27 10:58   ` Ludovic Courtès
2020-12-11  7:34     ` bug#33338: " Arun Isaac

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=875zwlgnnw.fsf@posteo.net \
    --to=brettg@posteo.net \
    --cc=33338@debbugs.gnu.org \
    --cc=somebody@not-sent-or-endorsed-by.tobias.gr \
    /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.