From: Leo Famulari <leo@famulari.name>
To: David Craven <david@craven.ch>
Cc: help-guix@gnu.org
Subject: Re: GuixSD on arm (ng0)
Date: Tue, 5 Jul 2016 13:02:29 -0400 [thread overview]
Message-ID: <20160705170229.GD2019@jasmine> (raw)
In-Reply-To: <CAL1_im=qTN2NaXOmXoff64OrDUWjFNaXn6qAX3==fHKpuy=NZQ@mail.gmail.com>
On Tue, Jul 05, 2016 at 03:04:56PM +0200, David Craven wrote:
> Just chiming in here...
>
> I know that github being propietary software probably won't be
> considered, but it is unarguably an awesome piece of software,
> possibly the best propietary software since google search :-) I think
> that using github would improve the efficiency of submitting/reviewing
> patches. But I'm still new to the sending patches via email thing - so
> I might get used to it...
I would really prefer to not have to use a web page for contributing to
Guix. I find the tools `git send-email` and `git am` to be very easy to
use and much faster than a web site.
The really nice thing about email is that one can do it with a *very*
wide variety of tools and interfaces. Web pages, on the other hand,
basically have a single interface, and you have to be a web developer to
change it for yourself.
But, some people don't prefer email. Considering that, my opinion is
that the ideal situation would be a hybrid mail / web interface, where
the two components could be used interchangeably. Work done on one
interface would automatically show up in the other interface. Does this
exist?
next prev parent reply other threads:[~2016-07-05 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 13:04 GuixSD on arm (ng0) David Craven
2016-07-05 17:02 ` Leo Famulari [this message]
2016-07-05 19:45 ` Alex Sassmannshausen
2016-07-05 22:54 ` David Craven
2016-07-05 20:54 ` ng0
-- strict thread matches above, loose matches on Subject: below --
2016-07-05 14:03 David Craven
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=20160705170229.GD2019@jasmine \
--to=leo@famulari.name \
--cc=david@craven.ch \
--cc=help-guix@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.
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).