all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs <emacs-devel@gnu.org>
Subject: Re: [Fwd: [arch-users] Re: Gud lord!]
Date: Mon, 9 Jun 2003 11:20:25 -0400	[thread overview]
Message-ID: <20030609152025.GA28948@gnu.org> (raw)
In-Reply-To: <20030609165127.2C8F.JMBARRANQUERO@laley.wke.es>

On Mon, Jun 09, 2003 at 05:00:16PM +0200, Juanma Barranquero wrote:
> > It's not optimal, and neither is working in an non source controlled
> > environment for developing substantial contributions.
> 
> No, it's not optimal, and certainly I don't remember having said it was.
> But even now there are people who does big contributions (I mean, not
> tiny patches of 5-10 lines, but changes of hundreds or thousands of
> lines) and who do not have write access nor (seem to) want it.

Indeed; I do a lot of development for projects where I don't have write
access (e.g., the linux kernel), and life is quite fine with a few shell
scripts to help me out.  Actually the thing which I find makes the most
difference is having at least read-only CVS access -- that's enough to make
it easy for me to keep things in sync and make patches; write access, by
comparison is rather a minor convenience.

[The time when I most appreciate having write access, actually, is when I
want to make a little random tweak (e.g. fix a typo), and don't have to
bother someone to check it in.]

I think for me, improvements in the standard patch-format to support things
like file renames would be at least important as a better revision control
system.  [Maybe arch actually addresses this, since I gather it tries to use
a very tool-oriented approach...]

-Miles
-- 
We live, as we dream -- alone....

  reply	other threads:[~2003-06-09 15:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08  1:09 [Fwd: [arch-users] Re: Gud lord!] Robert Anderson
2003-06-08  3:05 ` Alan Shutko
2003-06-08  5:01   ` Robert Anderson
2003-06-08 15:54     ` Stefan Monnier
2003-06-08 17:26       ` Robert Anderson
2003-06-09  8:23     ` Juanma Barranquero
2003-06-09 14:37       ` Robert Anderson
2003-06-09 15:00         ` Juanma Barranquero
2003-06-09 15:20           ` Miles Bader [this message]
2003-06-09 19:21           ` Jonathan Walther
2003-06-09 19:58             ` Stefan Monnier
     [not found]             ` <20030609214121.77EE.LEKTU@terra.es>
2003-06-09 20:11               ` Jonathan Walther
2003-06-10  7:14                 ` Juanma Barranquero
2003-06-10 12:59                   ` Miles Bader
2003-06-10 14:05                     ` Juanma Barranquero
2003-06-10 14:37                       ` Stefan Monnier
2003-06-10 14:55                         ` Juanma Barranquero
2003-06-10 15:03                           ` Stefan Monnier
2003-06-11  6:59                             ` Juanma Barranquero
2003-06-11 14:11                               ` Stefan Monnier
2003-06-11 14:40                                 ` Juanma Barranquero
2003-06-10 20:16                           ` Miles Bader
2003-06-11  7:10                             ` Juanma Barranquero
2003-06-10 14:54                       ` Robert Anderson
2003-06-11  0:25                   ` Richard Stallman
2003-06-11  7:19                     ` Juanma Barranquero
2003-06-11  9:54                       ` Jonathan Walther
2003-06-10  1:22           ` Robert Anderson
2003-06-10  6:53             ` Juanma Barranquero
2003-06-10 14:16               ` Robert Anderson
2003-06-08 15:51   ` Stefan Monnier
2003-06-09  1:18   ` Jonathan Walther
2003-06-09  1:47     ` Alan Shutko
2003-06-09  2:03       ` Jonathan Walther
2003-06-09 14:53       ` Robert Anderson
2003-06-09 15:20         ` Kai Großjohann
2003-06-10  0:35           ` Alex Schroeder
2003-06-10  6:12             ` Kai Großjohann

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030609152025.GA28948@gnu.org \
    --to=miles@gnu.org \
    --cc=emacs-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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.