From: Juanma Barranquero <lektu@terra.es>
Cc: emacs-devel@gnu.org
Subject: Re: [Savannah-hackers] [alexl@users.sourceforge.net: Jan's Gtk CVS notifications...?]
Date: Thu, 23 Jan 2003 14:58:08 +0100 [thread overview]
Message-ID: <20030123145449.FEDF.LEKTU@terra.es> (raw)
In-Reply-To: <20030123120046.B397@fe.up.pt>
On Thu, 23 Jan 2003 12:00:46 +0000, "Jaime E. Villate" <villate@gnu.org> wrote:
> What I can tell you is that there are three Emacs developers (lektu, kfstorm
> and handa) whose commits may stop sending e-mail notifications at any time,
> because they continue to use the old CVS repository, rather than the new one,
> in spite of the warnings given when they commit to the old repository.
I don't get any warning when commiting, perhaps because I never do a cvs
commit directly, but through Emacs CVS support...
> The old repository (/home/cvs/emacs or /cvs/emacs) is a symbolic link to the
> new one (/cvsroot/emacs), so the files are committed in the same place, but
> the CVSROOT files for both repositories are different and they have separate
> history files. If the two CVSROOTs ever become out of sync, CVS
> may start behaving differently for those 3 developers than for the rest.
I would be glad to set up things properly on my side, if I knew how.
Moreover, if accesing the new repository involves using ssh things can
get rough (I'm on Windows). Any information/help is welcome.
/L/e/k/t/u
next prev parent reply other threads:[~2003-01-23 13:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18bcI9-0007hg-00@fencepost.gnu.org>
2003-01-23 12:00 ` [Savannah-hackers] [alexl@users.sourceforge.net: Jan's Gtk CVS notifications...?] Jaime E. Villate
2003-01-23 13:58 ` Juanma Barranquero [this message]
2003-01-23 14:57 ` Jaime E. Villate
2003-01-23 23:24 ` Kenichi Handa
2003-01-24 1:26 ` Jaime E . Villate
2003-01-24 13:12 ` Kim F. Storm
2003-01-24 18:54 ` Eli Zaretskii
2003-01-24 21:44 ` Kim F. Storm
2003-01-25 16:56 ` Eli Zaretskii
2003-01-25 18:08 ` Rudy Gevaert
2003-01-25 17:19 ` Eli Zaretskii
2003-01-25 18:28 ` Rudy Gevaert
2003-01-26 5:46 ` Eli Zaretskii
2003-01-25 18:16 ` Mathieu Roy
2003-03-12 19:11 ` Eli Zaretskii
2003-01-26 15:37 ` [Savannah-hackers] " Richard Stallman
2003-01-27 10:29 ` Jaime E. Villate
2003-01-29 0:04 ` Richard Stallman
2003-01-25 19:23 ` Richard Stallman
2003-01-24 10:50 ` Juanma Barranquero
2003-01-23 18:06 ` Kim F. Storm
2003-01-23 17:22 ` Mathieu Roy
2003-01-23 18:39 ` Jaime E . Villate
2003-01-24 17:15 ` [Savannah-hackers] " Richard Stallman
2003-01-22 2:51 Jan's Gtk CVS notifications...? Alex Lancaster
2003-01-23 8:00 ` Richard Stallman
2003-01-23 18:22 ` Jan D.
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=20030123145449.FEDF.LEKTU@terra.es \
--to=lektu@terra.es \
--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 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).