From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: corrupted ,v files break cvs-to-git mirror
Date: Wed, 29 Aug 2007 11:04:35 +0200 [thread overview]
Message-ID: <46D536A3.3010908@swipnet.se> (raw)
In-Reply-To: <buoejhmvinu.fsf@dhapc248.dev.necel.com>
Miles Bader skrev:
> Jim Meyering <jim@meyering.net> writes:
>> Does anyone here have any idea how that happened?
>> FYI, here's the second "1.1" log entry, from "cvs log" output:
>> [What does "Moved" mean? ]
>>
>> ----------------------------
>> revision 1.1
>> date: 2005/08/23 20:05:32; author: jhd; state: Exp;
>> Moved from international. Old log:
>> ;;; swedish.el --- miscellaneous functions for dealing with Swedish.
>> ----------------------------
>> revision 1.12
>> date: 2005/07/04 17:22:27; author: lute; state: Exp; lines: +2 -2
>> Update FSF's address.
>> ----------------------------
>>
>> I hope it's easily fixed.
>
> It looks as if the stuff past "Moved old log:" are _not_ actual CVS
> revisions, but all part of the _log message_ for revision 1.1 -- i.e.,
> the person who did the "move" just copied the entire CVS log of from the
> old location verbatim, and stuffed into his log entry.
Yes, I did that. How else can we preserve the CVS log when moving files? But
I guess the whole file can be removed, it was obsolete in emacs 22.1, so for
23.1 it should be OK to remove, no?
Jan D.
next prev parent reply other threads:[~2007-08-29 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 8:34 corrupted ,v files break cvs-to-git mirror Jim Meyering
2007-08-29 8:39 ` Miles Bader
2007-08-29 9:04 ` Jan Djärv [this message]
2007-08-29 9:34 ` David Kastrup
2007-08-29 9:55 ` Jan Djärv
2007-08-29 9:40 ` Andreas Schwab
2007-08-29 15:06 ` Stefan Monnier
2007-08-30 7:58 ` Jim Meyering
2007-08-30 7:25 ` Jim Meyering
2007-08-30 21:38 ` emacs.git is in sync again [Re: corrupted , v " Jim Meyering
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=46D536A3.3010908@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=miles@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.