unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: Miles Bader <miles@gnu.org>, Richard Stallman <rms@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Plague of dashes in command echo
Date: Tue, 13 Jul 2004 18:15:00 -0400	[thread overview]
Message-ID: <20040713221500.GB19484@fencepost> (raw)
In-Reply-To: <lorentey.g.e.devel.87hdsb6emc.elte@eris.elte.hu>

On Tue, Jul 13, 2004 at 06:44:43PM +0200, L?rentey K?roly wrote:
> I think it would be desirable to preserve Arch metadata if I am to get
> commit access, but that means my patches would need to go through
> Miles's archive and I don't know how to do that.  Miles?

Well I'd love to have (1) an archive writable by others, but you'd have to
have a gnu account for that, and there are probably details to be worked out
(like group privs or something), or (2) some sort of patch-queue manager, but
that requires work to set up, and maybe some system privs.

But for now you can just send me a (tarred-up) changeset, and I'll apply it.

Either:

  * Make the changes without committing, and do `tla undo -o CSET'

  * Commit to some branch and, send me that changeset instead.

         `tla get-changeset REVISION CSET'
      or `tla delta REVISION1 REVISION2 CSET'
      or if it's a clean branch (no extraneous changes),
         `tla changes -o CSET miles@gnu.org--gnu-2004/emacs--cvs-trunk--0'

-Miles
-- 
/\ /\
(^.^)
(")")
*This is the cute kitty virus, please copy this into your sig so it can spread.

      reply	other threads:[~2004-07-13 22:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12  5:00 Plague of dashes in command echo Lőrentey Károly
2004-07-12 23:58 ` Richard Stallman
2004-07-13 16:44   ` Lőrentey Károly
2004-07-13 22:15     ` Miles Bader [this message]

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20040713221500.GB19484@fencepost \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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/emacs.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).