largefiles extension

Carter, Eli Eli.Carter at tektronix.com
Wed Aug 31 17:40:22 CDT 2011


.... and committing a 3.5GB largefile file causes problems in the dirstate code.

> -----Original Message-----
> From: Carter, Eli
> Sent: Wednesday, August 31, 2011 3:35 PM
> To: Carter, Eli; Mercurial-devel at selenic.com
> Subject: RE: largefiles extension
> 
> A few more things I found trying this out:
> 
> 1.   running the server as apache on Fedora, $HOME is not set, which makes
> lfutil.py's systemcachepath ()'s call to os.path.join() blow up because
> os.getenv('HOME') returns None.
> 2.   trying to clone a repo with largefiles using an hg without the largefiles
> extension enabled gives a rather unhelpful traceback about "TypeError: Odd-
> length string"
> 3.  trying to push a revision with largefiles to a server gives "abort:
> remotestore: could not put .... to remote store http://..." when pushing a
> revision that does not have largefiles would instead give the error "remote:
> ssl required"
> 
> Hopefully those are straightforward to correct... they certainly make getting
> started with largefiles more frustrating than it needs to be.
> 
> HTH,
> 
> Eli
> 
> > -----Original Message-----
> > From: mercurial-devel-bounces at selenic.com [mailto:mercurial-devel-
> > bounces at selenic.com] On Behalf Of Carter, Eli
> > Sent: Wednesday, August 31, 2011 1:28 PM
> > To: Mercurial-devel at selenic.com
> > Subject: largefiles extension
> >
> > I just found the discussion of the largefiles extension being proposed
> > for Mercurial's November release.  (
> > http://markmail.org/thread/mi4fubexskuu6lo7 )
> >
> > First, a small bugreport: in 'usage.txt', s/pattens/patterns/
> >
> > Secondly, the 'hg add --large ...." should have an inverse option
> > (like "--no- large").  Given a repository with existing largefiles,
> > new files over 10M
> > (default) are automatically added as largefiles.  If you also have an
> > over-sized text file that you _do_ want tracked normally, you'll have some
> challenges.
> > I've seen things like SQL initialization scripts, or generated sources
> > (which is a rant for another day...), or books
> > (http://www.gutenberg.org/ebooks/29765) get rather large while still
> > being files you want to edit and merge.
> > Similarly, the [largefiles].patterns should probably have
> > [largefiles].excludes so you could specify that *.sql or *.c or *.txt
> > files would never be treated as largefiles, even if they exceed the size
> boundary.
> >
> > HTH,
> >
> > Eli
> >
> > _______________________________________________
> > Mercurial-devel mailing list
> > Mercurial-devel at selenic.com
> > http://selenic.com/mailman/listinfo/mercurial-devel




More information about the Mercurial-devel mailing list