[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mercurial
Subject:    Re: Checking out a repository that requires largefiles to be enabled
From:       Augie Fackler <raf () durin42 ! com>
Date:       2015-03-30 12:44:21
Message-ID: E14D60C0-5427-4FF0-8CBB-4F00731DF6C2 () durin42 ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Mar 30, 2015, at 4:55 AM, anatoly techtonik <techtonik@gmail.com> wrote:

> Cool. Just to make it 100% sure about how it works, if I clone the repo with \
> largefiles without necessary flags, which of the following happens: 
> 1. hg fails
> 2. hg tells me that repo uses largefiles
> 3. hg tells me to use `--config extensions.largefiles=`
> 
> Is it 1,2,3 or just 1,2?

I think it’s actually “None of the above”. If you do ‘hg clone’, it doesn’t know to \
look for largefiles goop. If you do ‘hg clone --config extensions.largefiles=‘ then \
Matt’s fixes make 3.4 keep largefiles enabled in the clone’s hgrc.

> 
> On Sat, Mar 28, 2015 at 3:38 AM, Matt Harbison <mharbison72@gmail.com> wrote:
> On Fri, 27 Mar 2015 06:07:08 -0400, anatoly techtonik <techtonik@gmail.com> wrote:
> 
> On Wed, Mar 25, 2015 at 8:41 PM, Matt Harbison <matt_harbison@yahoo.com>
> wrote:
> 
> On Mar 25, 2015 1:33 PM, Mathias De Maré <mathias.demare@gmail.com>
> wrote:
> 
> 
> On Wed, Mar 25, 2015 at 2:24 PM, anatoly techtonik <techtonik@gmail.com>
> wrote:
> 
> Hi,
> 
> http://mercurial.selenic.com/wiki/LargefilesExtension
> 
> What will happen if I checkout repo that relies on
> largefilles without enabling this extension?
> 
> I believe only a .hglf file will be added, no actual largefiles.
> 
> 
> Is it possible to server side HG to give a warning
> and for client side to specify clone --large option
> to make the extension automatically enabled on
> checkout?
> 
> Matt made a change for this (should end up in 3.4):
> changeset:   24029:e1dbe0b215ae
> user:        Matt Harbison <matt_harbison@yahoo.com>
> date:        Mon Feb 02 19:58:41 2015 -0500
> summary:     largefiles: set the extension as enabled locally after a
> clone requiring it
> 
> Greetings,
> Mathias
> 
> The clone will fail, complaining about an unknown feature 'largefiles'.
> The change referenced above is simply to enable largefiles in the clone's
> hgrc, if required, so that the user doesn't have to.
> 
> 
> That's nice. I can't test it right now. So will 3.4 complain about unknown
> feature or enable it in clone's hgrc automatically?
> 
> You need to enable it during the clone (e.g. '--config extensions.largefiles=' on \
> the command line), but after that, that repo remembers to enable largefiles \
> automatically. 
> --Matt
> 
> 
> 
> -- 
> anatoly t.
> _______________________________________________
> Mercurial mailing list
> Mercurial@selenic.com
> http://selenic.com/mailman/listinfo/mercurial


["signature.asc" (signature.asc)]

-----BEGIN PGP SIGNATURE-----

iQIcBAEBAgAGBQJVGUUlAAoJELnJ3IJKpb3VfMMP/1rQgkJhG1VO8gRQ+/0DZmWm
c/ww4bsjpvkJ0UmwhWhojRj0BsXvRTO0YZf9f+tzGDjZ2XlcTs0E/84BR8TCFt4o
sJu8YqZ52vpcr2hUvjDTs54jY1OPLG+58Nulnp1r6smlJVLJz2CYqBpwQcRiHIzh
lrNKQll5q5iaJJ7s6fSydUQvEC7VewyFRBiOtlSzZtMGVjZI6SBhkMxjYFpEB4BG
51o8ihSj7e5SxBoW+MqIEiK3g14UoLRr2yG7TAmqIxfvRKSdABaRsD5ugMSiKtcz
wGyPlaqfSBbu5OkEgDUYDhokhwhv6dKK2P5YDmpq8KrKk74w4gc2+89p8LPk3e9R
0yW2vLbTxEkwh97lGq9Jd2jLp7NqbpOXIdCGe+IRbzKC5rn8aQngLjTcizR4PvYT
LJy73DoK7hb8Fxe2Z+YzeNx3UQvHRThit4r3ddu2xvIBV9q53fZuLLDGe8Y7f0S4
hq8/5XMWPpGPUNe8FrPWuopM3ZGdlLPadRhuW0kKFwchuf8eZY2U5hwCEGQGTa2w
Bx21jeyQMOqtuoPnlRpyQDMDilK0Gr4P0hN5rwsKstHVJaqGKUX/PiK48ece+4me
5zKf3DmRY4DPxMKXXE1649dQeLltRc9+fkTHFznIoS45PppyjUBH34/ItT621ZN/
MeryFbpwtbLa4dF5zDYD
=t2ga
-----END PGP SIGNATURE-----

[Attachment #6 (text/plain)]

_______________________________________________
Mercurial mailing list
Mercurial@selenic.com
http://selenic.com/mailman/listinfo/mercurial


[prev in list] [next in list] [prev in thread] [next in thread]