All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Thompson <andrewkt@aktzero.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Mercurial List <mercurial@selenic.com>
Subject: Re: bitkeeper gone in 2 weeks - which RCS?
Date: Wed, 15 Jun 2005 17:45:56 -0400	[thread overview]
Message-ID: <42B0A194.80903@aktzero.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282262@liverpoolst.ad.cl.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

I thought I'd let this simmer a while on the hg list, but here's a 
little snippet:

Ian Pratt wrote:
>>>It's just annoying that it currently lacks renames
>>
>>I wonder how hard it would be to get these added.  Guess I'll 
>>have to talk with Matt ;)
> 
> Because of the way we use renames when doing linux version upgrades it
> would be really useful to get this added.

Matt Mackall wrote:
 > Well someone can relay to them that rename support should happen very
 > soon. I'm still not convinced of the value of per-file checkins (if
 > you need per-file checkins, your commits are too big) but I'm not
 > completely immune to reason.


-- 
Andrew Thompson
http://aktzero.com/

[-- Attachment #2: andrewkt.vcf --]
[-- Type: text/x-vcard, Size: 153 bytes --]

begin:vcard
fn:Andrew Thompson
n:Thompson;Andrew
email;internet:andrewkt@aktzero.com
x-mozilla-html:FALSE
url:http://aktzero.com/
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2005-06-15 21:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 21:35 bitkeeper gone in 2 weeks - which RCS? Ian Pratt
2005-06-15 21:45 ` Andrew Thompson [this message]
2005-06-16  2:56   ` Rusty Russell
     [not found] ` <mailman.1118871375.26501@unix-os.sc.intel.com>
2005-06-16 18:34   ` Arun Sharma
2005-06-20 20:39 ` Paul Larson
2005-06-20 20:44   ` Rik van Riel
2005-06-20 20:54   ` Josh Triplett
2005-06-20 21:01   ` Andrew Thompson
2005-06-20 21:28     ` Paul Larson
     [not found]   ` <mailman.1119300279.12847@unix-os.sc.intel.com>
2005-06-20 21:03     ` Arun Sharma
2005-06-20 21:08       ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2005-06-21  0:16 Soh Tk-r28629
2005-06-21  0:29 ` Matt Mackall
2005-06-15 22:11 Ian Pratt
2005-06-16  1:16 ` Matt Mackall
2005-06-16  1:21   ` Rik van Riel
2005-06-15 23:03     ` Christopher Li
2005-06-16 11:36       ` Theodore Ts'o
2005-06-15 19:45 Ian Pratt
2005-06-15 20:10 ` Rik van Riel
2005-06-14 19:09 Rik van Riel
2005-06-14 19:26 ` Paul Larson
2005-06-14 19:27   ` Ronald G. Minnich
     [not found]   ` <mailman.1118777276.15947@unix-os.sc.intel.com>
2005-06-14 19:43     ` Arun Sharma
2005-06-14 19:50       ` Paul Larson
2005-06-14 19:58         ` Arun Sharma
2005-06-14 23:31           ` aq
2005-06-14 23:50             ` Rusty Russell
2005-06-15  7:09               ` Michael Paesold
2005-06-16  2:37                 ` Ronald G. Minnich
2005-06-16 11:51                   ` David Hopwood
2005-06-15 19:18             ` Rik van Riel
2005-06-14 19:52       ` Ronald G. Minnich
2005-06-14 19:54         ` Arun Sharma
2005-06-15  7:51 ` Gerd Knorr

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=42B0A194.80903@aktzero.com \
    --to=andrewkt@aktzero.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=mercurial@selenic.com \
    --cc=xen-devel@lists.xensource.com \
    /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.
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.