From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <marius@gnu.org>, Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.
Date: Mon, 09 Nov 2020 08:12:19 +0100 [thread overview]
Message-ID: <861rh3ypf0.fsf@gmail.com> (raw)
In-Reply-To: <87tutzg9pj.fsf@gnu.org>
Hi Pierre,
On Sun, 08 Nov 2020 at 16:16, Marius Bakke <marius@gnu.org> wrote:
>> Out of curiosity: how do commit messages help you here?
>
> It can be difficult to tell from the diff alone which inputs are native,
> regular, or propagated.
I had similar difficulties when looking at #31108. It is easier to find
which commit add/remove/replace what by simply reading the commit
message than to read the diff (raw). And sometimes the diff is not
enough because there is not enough context and I had to open the file at
the specified commit. It is no extra time when the commiter does and it
saves a lot of time when someone parse the history. IMHO.
<http://issues.guix.gnu.org/issue/31108>
All the best,
simon
next prev parent reply other threads:[~2020-11-09 7:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201020130843.10939.42161@vcs0.savannah.gnu.org>
2020-11-07 19:39 ` branch master updated: gnu: nyxt: Update to 2-pre-release-3 Marius Bakke
2020-11-07 19:46 ` Marius Bakke
2020-11-08 9:40 ` Pierre Neidhardt
2020-11-08 15:16 ` Marius Bakke
2020-11-09 7:12 ` zimoun [this message]
2020-11-09 9:29 ` Pierre Neidhardt
2020-11-09 21:14 ` Marius Bakke
2020-11-09 22:38 ` Marius Bakke
2020-11-10 9:01 ` Pierre Neidhardt
2020-11-10 9:28 ` Pierre Neidhardt
2020-11-10 19:22 ` Marius Bakke
2020-11-10 19:59 ` Pierre Neidhardt
2020-11-10 20:28 ` Marius Bakke
2020-11-11 9:19 ` Pierre Neidhardt
2020-11-11 12:43 ` Pierre Neidhardt
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=861rh3ypf0.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=marius@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).