From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Upgrade bedtools to 0.25.0.
Date: Sat, 09 Jan 2016 18:48:03 +0100 [thread overview]
Message-ID: <87d1tabq5o.fsf@gnu.org> (raw)
In-Reply-To: <20160109163715.GA12060@debian> (Andreas Enge's message of "Sat, 9 Jan 2016 17:37:15 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> I do not have very strong feelings about the matter, but I do see the point
> of separating stylistic and syntactic changes on one hand from functional
> changes on the other hand. Then one can simply accept the former without
> further checking; and the latter does not require any checking since only
> the version and the hash line have changed.
Right. Another practical advantage is that, should the upgrade cause
problems, we can simply revert the commit that does the upgrade without
losing the other change.
Ludo’.
next prev parent reply other threads:[~2016-01-09 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 6:47 [PATCH] Upgrade bedtools to 0.25.0 Ben Woodcroft
2016-01-09 9:54 ` Andreas Enge
2016-01-09 13:44 ` Pjotr Prins
2016-01-09 16:37 ` Andreas Enge
2016-01-09 17:48 ` Ludovic Courtès [this message]
2016-01-09 18:07 ` Ricardo Wurmus
2016-01-09 20:32 ` Leo Famulari
2016-01-10 14:39 ` Ben Woodcroft
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=87d1tabq5o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--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).