On Mar 1, 3:21 pm, Ben Collins-Sussman suss...@google.com wrote:
You're trying to commit from an old working copy to a newly-created
repository?
Correct. I created the new project, changed PyWhip to PyKata in the
working copy,and now I'm trying to upload (commit) the edited working
copy to the
Sounds to me like it might be simpler to svnsync from Google Code to your
local harddisk and then svnsync back up to Google Code in the new project.
:-)
On Tue, Mar 2, 2010 at 1:57 PM, Dr Dave macqu...@box67.com wrote:
On Mar 1, 3:21 pm, Ben Collins-Sussman suss...@google.com wrote:
You're
Hi there,
For documenting the underlying database of our system, I am creating
database diagrams and storing them in our code repository (in an 'admin'
dir). The file is:
i'm thinking byte size.
On 2 March 2010 12:13, Darren Pearce-Lazard darren.pea...@gmail.com wrote:
Hi there,
For documenting the underlying database of our system, I am creating
database diagrams and storing them in our code repository (in an 'admin'
dir). The file is:
i'm thinking byte size.
I assumed it was resolution since a png image that is quite small (in terms
of dimensions) but consists of many colours can be a lot larger than a jpg
for the same image. Maybe it's a combination of the two. We'll have to wait
and see. :-)
Cheers,
:Darren.
--
It's the size in bytes. Serving large files ties up resources for much
longer so we set limits on how large a file we will display in the web
interface.
Nathan
On Tue, Mar 2, 2010 at 12:53 PM, Darren Pearce-Lazard
darren.pea...@gmail.com wrote:
i'm thinking byte size.
I assumed it was
It's the size in bytes. Serving large files ties up resources for much
longer so we set limits on how large a file we will display in the web
interface.
Ah ok. :-) You win, Charles. ;-)
What is the limit? 1Mb?
Many thanks, Nathan.
:D
--
On Tue, Mar 2, 2010 at 1:00 PM, Darren Pearce-Lazard
darren.pea...@gmail.com wrote:
It's the size in bytes. Serving large files ties up resources for much
longer so we set limits on how large a file we will display in the web
interface.
Ah ok. :-) You win, Charles. ;-)
What is the limit?
Click on the link View Raw File.
On 2 March 2010 12:13, Darren Pearce-Lazard darren.pea...@gmail.com wrote:
Hi there,
For documenting the underlying database of our system, I am creating
database diagrams and storing them in our code repository (in an 'admin'
dir). The file is:
Ah ok. :-) You win, Charles. ;-)
What is the limit? 1Mb?
Many thanks, Nathan.
:D
Approximately, yes. It is subject to change as we tune our
infrastructure over time though.
Ok. Thanks for letting me know.
Cheers,
:Darren.
--
Click on the link View Raw File.
Yep. Knew about that but didn't want my users to have the extra click. :-)
Anyhow, at least for the time being, keeping the file within 1Mb looks to be
the way to go.
Take care,
:Darren.
--
Ah, ER diagrams. Brings back some memories.
I suppose the file size limitation is to minimize server load.
Good luck with your project.
On 2 March 2010 14:17, Darren Pearce-Lazard darren.pea...@gmail.com wrote:
Click on the link View Raw File.
Yep. Knew about that but didn't want my users
Ah, ER diagrams. Brings back some memories.
Happy ones, of course. ;-)
I suppose the file size limitation is to minimize server load.
Exactly.
Good luck with your project.
Thanks, Charles. Good luck with your project(s) too.
:Darren.
--
:
Sounds to me like it might be simpler to svnsync from Google Code to your
local harddisk and then svnsync back up to Google Code in the new project.
I'm using TortoiseSVN on Windows XP. There is nothing in Tortoise
that I can find to do an svnsync or replicate repository. I
already have a
I guess things are a little bigger on your disk than mine -- all the
changes for openwonderland squeaked in, but avatars didn't quite make
it. Can we get another 1GB on openwonderland and openwonderland-
avatars?
Thanks again!
-Jon
On Mar 1, 5:02 am, Nathaniel Manista nathan...@google.com
On Tue, Mar 2, 2010 at 2:39 PM, Jonathan jonathan...@gmail.com wrote:
I guess things are a little bigger on your disk than mine -- all the
changes for openwonderland squeaked in, but avatars didn't quite make
it. Can we get another 1GB on openwonderland and openwonderland-
avatars?
Thanks
I bet it's those squirrels taking a cut of the megabytes again. They're
great for moving hard drives around in the datacenters, but they're addicted
to the storage you see. It's quite ugly, but we humor them.
Added another 2G to each project, to give you breathing room. Enjoy!
- Dave
On Tue,
svnsync has nothing to do with this; that's a way of sucking out the
*entire repository* to local disk. Totally irrelevant to the problem
at hand.
Working copies are glued to their original repositories in multiple
secret ways: the original checkout URL is embedded deep within every
secret
Oh, sorry. Seems I had this completely wrong. I should have read the
original post more thoroughly. Please ignore my svnsync suggestion.
My apologies. :-)
:Darren.
On Tue, Mar 2, 2010 at 9:35 PM, Ben Collins-Sussman suss...@google.comwrote:
svnsync has nothing to do with this; that's a way
Thanks, Ben. Your help is much appreciated.
On Mar 2, 2:35 pm, Ben Collins-Sussman suss...@google.com wrote:
Working copies are glued to their original repositories in multiple
secret ways: the original checkout URL is embedded deep within every
secret .svn/ metadata directory in every
On Tue, Mar 2, 2010 at 6:33 PM, Dr Dave macqu...@box67.com wrote:
Thanks, Ben. Your help is much appreciated.
On Mar 2, 2:35 pm, Ben Collins-Sussman suss...@google.com wrote:
Working copies are glued to their original repositories in multiple
secret ways: the original checkout URL is
In roughly 3 months, we'll release a modified version of the image under
the Creative Commons license.
That day has finally arrived! The image is linked from
http://code.google.com/codejam/archive.html under 2009.
Cheers,
Bartholomew
--
You received this message because you are subscribed
22 matches
Mail list logo
