From: Eric Bavier <ericbavier@centurylink.net>
To: 37965@debbugs.gnu.org
Subject: bug#37965: parse-error in latest news entry
Date: Mon, 28 Oct 2019 16:27:43 -0400 (EDT) [thread overview]
Message-ID: <1018582292.389516.1572294463512.JavaMail.zimbra@centurylink.net> (raw)
In-Reply-To: <handler.37965.B.157228187825626.ack@debbugs.gnu.org>
FWIW, hacky way to check news items in shell:
```
commit=HEAD
previous=$(git rev-parase ${commit}^)
guix pull --url="file://$PWD" --commit="$previous" --profile=$PWD/_pull_check
guix pull --uri="file://$PWD" --commit="$commit" --profile=$PWD/_pull_check
guix pull --profile=$PWD/_pull_check --news
rm -rf $PWD/_pull_check
```
`~Eric
----- On Oct 28, 2019, at 4:58 PM, GNU bug Tracking System help-debbugs@gnu.org wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> bug-guix@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 37965@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 37965: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37965
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
--
`~Eric
next prev parent reply other threads:[~2019-10-28 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 16:57 bug#37965: parse-error in latest news entry Eric Bavier
[not found] ` <handler.37965.B.157228187825626.ack@debbugs.gnu.org>
2019-10-28 20:27 ` Eric Bavier [this message]
2019-10-28 20:59 ` Eric Bavier
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=1018582292.389516.1572294463512.JavaMail.zimbra@centurylink.net \
--to=ericbavier@centurylink.net \
--cc=37965@debbugs.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).