From: Mark H Weaver <mhw@netris.org>
To: David Hashe <david.hashe@dhashe.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: brasero: Update to 3.12.1, Add inputs.
Date: Fri, 10 Jul 2015 01:01:35 -0400 [thread overview]
Message-ID: <87y4iomwr4.fsf@netris.org> (raw)
In-Reply-To: <CAAn-YqH87YvELsF=JBL4cWwm0h_MXgVi0EoLONRpfascf0ui0w@mail.gmail.com> (David Hashe's message of "Thu, 9 Jul 2015 23:05:18 -0500")
David Hashe <david.hashe@dhashe.com> writes:
> I already have my copyright line in this particular file, since I've
> submitted to it before.
Ah, indeed. Pushed, thanks!
Mark
prev parent reply other threads:[~2015-07-10 5:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 4:40 [PATCH] gnu: brasero: Update to 3.12.1, Add inputs David Hashe
2015-07-09 5:34 ` Mark H Weaver
2015-07-10 4:05 ` David Hashe
2015-07-10 5:01 ` Mark H Weaver [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=87y4iomwr4.fsf@netris.org \
--to=mhw@netris.org \
--cc=david.hashe@dhashe.com \
--cc=guix-devel@gnu.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.
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).