From: Leo Famulari <leo@famulari.name>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add slurm.
Date: Sat, 13 Feb 2016 16:43:38 -0500 [thread overview]
Message-ID: <20160213214338.GA10825@jasmine> (raw)
In-Reply-To: <20160213213201.GA20467@thebird.nl>
On Sat, Feb 13, 2016 at 10:32:01PM +0100, Pjotr Prins wrote:
> On Sat, Feb 13, 2016 at 03:38:46PM -0500, Leo Famulari wrote:
> > I wonder if the version of git is a factor? 2.1.4 vs 2.6.3. Jan was also
> > using 2.1.4, and his patches also failed *only* on the attribution line.
>
> Thank you Leo and Andreas for restoring my sanity!
>
> I'll upgrade git. I was using the newer version in my build
> environment but generating the patch in an older version. Also locales
> I need to settle on. I tend to have en_GB on Debian, but in a guix
> shell it may act strange if I don't specify locales.
>
> And I won't add attribution again ;). I.e., the combination of being
> an old git, having wrong locales and injecting self-attribution, was
> lethal.
Does this mean the old version of git doesn't generate patches with the
correct locale?
I wonder... where is everyone getting git 2.1.4 from? It's 2 years old
;)
>
> Pj.
next prev parent reply other threads:[~2016-02-13 21:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:36 [PATCH] gnu: Add slurm-llnl Pjotr Prins
2016-02-11 4:04 ` Eric Bavier
2016-02-11 8:15 ` Pjotr Prins
2016-02-11 10:08 ` Andreas Enge
2016-02-11 11:11 ` Pjotr Prins
2016-02-11 14:21 ` Andreas Enge
2016-02-11 15:00 ` Pjotr Prins
2016-02-12 12:30 ` Pjotr Prins
2016-02-11 15:19 ` Eric Bavier
2016-02-12 12:20 ` Pjotr Prins
2016-02-12 12:30 ` Andreas Enge
2016-02-12 12:31 ` Pjotr Prins
2016-02-12 12:57 ` [PATCH] gnu: Add slurm-wlm Pjotr Prins
2016-02-12 17:51 ` Andreas Enge
2016-02-13 8:59 ` [PATCH] gnu: Add slurm Pjotr Prins
2016-02-13 10:28 ` Andreas Enge
2016-02-13 16:42 ` Pjotr Prins
2016-02-13 17:00 ` Andreas Enge
2016-02-13 17:01 ` Pjotr Prins
2016-02-13 17:20 ` Andreas Enge
2016-02-13 20:13 ` Leo Famulari
2016-02-13 20:34 ` Andreas Enge
2016-02-13 20:40 ` Leo Famulari
2016-02-14 14:22 ` Andreas Enge
2016-02-14 19:08 ` Leo Famulari
2016-02-15 12:09 ` Pjotr Prins
2016-02-15 21:51 ` Andreas Enge
2016-02-16 7:21 ` Pjotr Prins
2016-02-16 9:55 ` Andreas Enge
2016-02-13 20:38 ` Leo Famulari
2016-02-13 21:32 ` Pjotr Prins
2016-02-13 21:43 ` Leo Famulari [this message]
2016-02-13 17:13 ` Pjotr Prins
2016-02-11 4:33 ` [PATCH] gnu: Add slurm-llnl Eric Bavier
2016-02-11 8:17 ` Pjotr Prins
2016-02-11 8:28 ` Ricardo Wurmus
2016-02-11 18:36 ` Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2016-02-13 17:22 [PATCH] gnu: Add slurm Pjotr Prins
2016-02-13 17:30 ` Andreas Enge
2016-02-13 17:21 Pjotr Prins
2016-02-13 17:21 Pjotr Prins
2016-02-13 17:18 Pjotr Prins
2016-02-13 17:14 Pjotr Prins
2015-12-28 22:00 swedebugia
2015-12-28 23:13 ` Eric Bavier
2015-12-29 4:31 ` Leo Famulari
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=20160213214338.GA10825@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).