From: David Kastrup <dak@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Jim Meyering <jim@meyering.net>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: emacs.git mirror status
Date: Fri, 14 Sep 2007 13:00:26 +0200 [thread overview]
Message-ID: <86r6l1qzp1.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <jezlzpa8yo.fsf@sykes.suse.de> (Andreas Schwab's message of "Fri\, 14 Sep 2007 11\:32\:15 +0200")
Andreas Schwab <schwab@suse.de> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> I am afraid that this is not feasible in the current state of affairs:
>> as long as all multi-tty material in the current trunk is only tracked
>> and blamed to a point where Miles was synching rather than the
>> original checkin, one can't seriously work with it. Presumably the
>> information loss is not yet there in the arch repository from Miles,
>> so one needs to either make cvsps understand the arch information
>> present in CVS ChangeLog entries, or import from arch rather than CVS.
>
> I have created an alternate GIT tree that is converted with a modified
> version of git-cvsimport. You can have a look at it at
> <http://ftp.suse.com/pub/people/schwab/emacs/emacs.git>. One advantage
> of this tree is that it contains some merge information gathered from
> the arch logs, and I have also corrected some author information. If it
> turned out to be useful I can provide the script and authors file I have
> used.
Well, if I use something like
git-gui --blame src/xterm.c
in the trunk, it is still Miles who indiscriminately gets all the
blame for multi-tty.
--
David Kastrup
next prev parent reply other threads:[~2007-09-14 11:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 8:03 emacs.git mirror status Jim Meyering
2007-09-14 8:14 ` dhruva
2007-09-14 8:27 ` Jim Meyering
2007-09-14 8:40 ` David Kastrup
2007-09-14 8:57 ` Jim Meyering
2007-09-14 9:32 ` Andreas Schwab
2007-09-14 9:45 ` David Kastrup
2007-09-14 9:56 ` Andreas Schwab
2007-09-14 9:49 ` Jim Meyering
2007-09-14 13:18 ` Andreas Schwab
2007-09-15 9:17 ` Jim Meyering
2007-09-15 10:01 ` Andreas Schwab
2007-09-16 7:02 ` Jim Meyering
2007-09-14 11:00 ` David Kastrup [this message]
2007-09-14 11:32 ` Andreas Schwab
2007-09-14 11:35 ` Andreas Schwab
2007-09-14 11:47 ` David Kastrup
2007-09-14 11:51 ` David Kastrup
2007-09-14 12:10 ` Andreas Schwab
2007-09-14 12:53 ` David Kastrup
2007-09-14 13:13 ` Andreas Schwab
2007-09-14 13:26 ` David Kastrup
2007-09-14 11:53 ` Andreas Schwab
2007-09-14 12:06 ` David Kastrup
2007-09-14 12:16 ` Andreas Schwab
2007-09-14 12:52 ` David Kastrup
2007-09-14 13:07 ` Andreas Schwab
2007-09-14 13:39 ` David Kastrup
2007-09-15 2:09 ` Richard Stallman
2007-09-15 5:49 ` David Kastrup
2007-09-15 2:09 ` Richard Stallman
2007-09-15 7:53 ` Andreas Schwab
2007-09-17 0:21 ` Richard Stallman
2007-09-17 0:35 ` Glenn Morris
2007-09-17 15:53 ` Richard Stallman
2007-09-17 16:04 ` David Kastrup
2007-09-17 18:08 ` Glenn Morris
2007-09-17 21:39 ` Stefan Monnier
2007-09-17 6:01 ` David Kastrup
2007-09-14 11:40 ` David Kastrup
2007-09-14 12:50 ` Andreas Schwab
2007-09-14 12:58 ` David Kastrup
2007-09-18 10:05 ` Andreas Schwab
2007-09-18 11:15 ` David Kastrup
2007-09-18 11:58 ` Andreas Schwab
2007-09-19 12:48 ` David Kastrup
2007-09-19 13:07 ` David Kastrup
2007-09-19 13:37 ` Andreas Schwab
2007-09-19 14:14 ` Jim Meyering
2007-09-19 14:21 ` David Kastrup
2007-09-19 14:23 ` Jim Meyering
2007-09-20 19:05 ` 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
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=86r6l1qzp1.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
--cc=schwab@suse.de \
/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).