unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: emacs-devel@gnu.org
Subject: Re: State of VC?
Date: Tue, 19 Feb 2008 07:44:35 -0800	[thread overview]
Message-ID: <200802191544.m1JFiaxd011829@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <87ir0lf3z6.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Tue, 19 Feb 2008 14:52:29 +0100")

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

  > () Dan Nicolaescu <dann@ics.uci.edu>
  > () Mon, 18 Feb 2008 09:40:31 -0800
  > 
  >    it made more sense to spend time writing proof of concept code,
  >    and there was little point to spend time writing ISO9000 type
  >    documents describing it.  On top of that, everything was
  >    discussed at length on the list.
  > 
  > All i ask for is some comments in the source code, as a courtesy
  > to anyone who has not followed the discussion.  I think a brief
  > summary (no need for a lot of spew) of the conclusions reached,
  > together w/ the code, would "prove" the concept better.

I added a description.
(Being less obnoxious about this would have been appreciated)

  >      > Personally, i don't think vc-directory for Git is that bad
  >      > (w/ some tweaking)[0].  
  >    You mean "vc-git-hacking"? That link does not work.
  > 
  > I see this:
  >  $ cd /tmp
  >  $ git clone http://www.gnuvola.org/wip/vc-git-hacking.git
  >  Initialized empty Git repository in /tmp/vc-git-hacking/.git/
  >  got 9e2f244ec65b24f8c78d3488ca506a3b5f2892e6
  >  walk 9e2f244ec65b24f8c78d3488ca506a3b5f2892e6
  >  got 340ef0ef0a358e20ef6a468a1ac57d538aa043bf
  >  got b8b0d6fe86d729b7faee7eee112d1844c8a1332b
  >  [...53 lines deleted...]
  > 
  > What do you see?

It works now, it used to give an error saying something about needing to
run update-server-info.




  reply	other threads:[~2008-02-19 15:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 16:43 State of VC? Eric S. Raymond
2008-01-22 17:08 ` Tom Tromey
2008-01-22 22:07   ` Dan Nicolaescu
2008-01-22 21:51     ` Tom Tromey
2008-01-23  2:31       ` Stefan Monnier
2008-01-23 19:01       ` Dan Nicolaescu
2008-01-25  0:17         ` Tom Tromey
2008-01-26 19:21           ` Dan Nicolaescu
2008-01-26 22:06             ` Eric S. Raymond
2008-02-17 18:16               ` Dan Nicolaescu
2008-02-17 18:24                 ` Thien-Thi Nguyen
2008-02-17 18:56                   ` Dan Nicolaescu
2008-02-18  8:03                     ` Thien-Thi Nguyen
2008-02-18  8:36                       ` Miles Bader
2008-02-18  8:48                         ` Thien-Thi Nguyen
2008-02-18  8:57                           ` Miles Bader
2008-02-18  9:18                             ` Thien-Thi Nguyen
2008-02-25 15:14                             ` Thien-Thi Nguyen
2008-02-18 17:40                       ` Dan Nicolaescu
2008-02-19 13:52                         ` Thien-Thi Nguyen
2008-02-19 15:44                           ` Dan Nicolaescu [this message]
2008-02-19 16:57                             ` Thien-Thi Nguyen
2008-02-19 20:53                               ` Dan Nicolaescu
2008-02-17 23:09                 ` Eric S. Raymond
2008-01-22 22:26     ` Glenn Morris
2008-01-23 13:01       ` Johan Bockgård
2008-01-24  7:07       ` Dan Nicolaescu
2008-01-24  8:58         ` Thien-Thi Nguyen
2008-01-24 14:57           ` Stefan Monnier
2008-01-24 15:09             ` Thien-Thi Nguyen
2008-01-25 22:47             ` Richard Stallman
2008-01-26  2:57               ` Stefan Monnier
2008-01-26  7:46         ` Alexandru Harsanyi
2008-01-24 13:23       ` Thien-Thi Nguyen

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=200802191544.m1JFiaxd011829@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=ttn@gnuvola.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).