From: David Craven <david@craven.ch>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: GHM debriefing
Date: Mon, 29 Aug 2016 14:48:14 +0200 [thread overview]
Message-ID: <CAL1_imn0XDOL-o=ZkPepw6OYtjtoZnk8xXwqEyy2EAMyuE8sHg@mail.gmail.com> (raw)
In-Reply-To: <87eg5769n9.fsf@gnu.org>
> Slides online, and hopefully videos will follow:
>
> https://www.gnu.org/software/guix/help/#talks
Nice slides!
> On that topic, I had an interesting discussion with Nicolas Petton of
> Emacs about patch tracking. Nicolas explained that Gitlab (free
> software) doesn’t have some of the technical defects that GitHub has; in
> particular it can rebase instead of merging, thereby helping preserve a
> linear history, and it can be dealt with “mostly” by email. Perhaps we
> could try running an instance and see what it’s like.
Calling it a technical defect is a little harsh... ;-) Gitlab is going to be an
improvement over the existing state of affairs. Just spent an hour fixing
the u-boot [0] patch manually to apply to a fresh tree. (Line wrapping mostly,
removing some hunks and adding a newline at the end)
[0] http://lists.gnu.org/archive/html/guix-devel/2016-07/msg01414.html
next prev parent reply other threads:[~2016-08-29 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 22:09 GHM debriefing Ludovic Courtès
2016-08-29 12:48 ` David Craven [this message]
2016-08-29 13:50 ` Vincent Legoll
2016-08-29 15:20 ` Christopher Allan Webber
2016-08-30 15:57 ` Ludovic Courtès
2016-08-31 13:40 ` ng0
2016-08-31 13:48 ` David Craven
2016-08-31 22:28 ` Clément Lassieur
2016-08-31 23:08 ` Leo Famulari
2016-09-01 6:41 ` ng0
2016-09-01 12:24 ` Ludovic Courtès
2016-09-03 8:05 ` Hartmut Goebel
-- strict thread matches above, loose matches on Subject: below --
2013-08-29 21:52 Ludovic Courtès
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='CAL1_imn0XDOL-o=ZkPepw6OYtjtoZnk8xXwqEyy2EAMyuE8sHg@mail.gmail.com' \
--to=david@craven.ch \
--cc=guix-devel@gnu.org \
--cc=ludo@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).