[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#49526: closed (Add cl-authentic)

From: GNU bug Tracking System
Subject: bug#49526: closed (Add cl-authentic)
Date: Mon, 12 Jul 2021 15:08:01 +0000

Your message dated Mon, 12 Jul 2021 15:07:23 +0000
with message-id <87wnpvvadw.fsf@kitej>
and subject line Re: [bug#49526] Add cl-authentic
has caused the debbugs.gnu.org bug report #49526,
regarding Add cl-authentic
to be marked as done.

(If you believe you have received this mail in error, please contact

49526: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=49526
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Add cl-authentic Date: Sun, 11 Jul 2021 18:30:33 +0000
Empty Message

Attachment: 0001-gnu-Add-cl-authentic.patch
Description: Text Data

--- End Message ---
--- Begin Message --- Subject: Re: [bug#49526] Add cl-authentic Date: Mon, 12 Jul 2021 15:07:23 +0000
Charles <charles.b.jackson@protonmail.com> skribis:

> Woops, yes. I forgot to pull to local before copying the comit and hash. I 
> have attatchhed an updated patch.
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Monday, July 12th, 2021 at 4:41 AM, Guillaume Le Vaillant <glv@posteo.net> 
> wrote:
>> When applying this patch, should I also update it to the most recent
>> upstream commit (d5ff2f4666ce24e41fb4ca22476c782c070e6f6e)?

Patch pushed as 62b60ba08249cbe239f3abe033a15fac83c4b54a.

Attachment: signature.asc
Description: PGP signature

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]