On 15/05/2014 23:39, Magnus Therning wrote:
On Thu, May 15, 2014 at 11:21:25PM +0100, Andy Hardy wrote:
On 15/05/2014 22:48, Magnus Therning wrote:
- version: doesn't make sense in git, would it be the hash?
what does that tell me?
I find an identifier useful when investigating problems
On Friday, May 16, 2014 12:52:44 AM UTC+2, Magnus Therning wrote:
I must say though that your example might constitute another argument
*against* having keywords, that sort of deployment process quickly
leads to a mess ;)
Yeah, the fallacy was that it was easier to deploy one file than to
On Fri, May 16, 2014 at 8:22 AM, Andy Hardy a...@hardyfamily.org.uk wrote:
On 15/05/2014 23:39, Magnus Therning wrote:
On Thu, May 15, 2014 at 11:21:25PM +0100, Andy Hardy wrote:
On 15/05/2014 22:48, Magnus Therning wrote:
- version: doesn't make sense in git, would it be the hash?
what does
On Friday, May 16, 2014 8:22:30 AM UTC+2, Andy wrote:
For a 'release' we'd send the customer a complete set of files, but
often a fix only requires one or two files to be modified which we ask
the customer to install. When a dealing with a later fault, we'd like to
have a method of knowing
#cat recipes-devtools/python/python-heat_git.bb.rej
diff
a/meta-openstack/recipes-devtools/python/python-heat_git.bbb/meta-openstack/recipes-devtools/python/
python-heat_git.bb(rejected hunks)
@@ -10,6 +10,9 @@ SRCNAME = heat
SRC_URI =
On Fri, 16 May 2014 17:21:10 +0800
lei yang yanglei.f...@gmail.com wrote:
#cat recipes-devtools/python/python-heat_git.bb.rej
diff
a/meta-openstack/recipes-devtools/python/python-heat_git.bbb/meta-openstack/recipes-devtools/python/
python-heat_git.bb(rejected hunks) @@ -10,6 +10,9 @@
From: John Fisher fishook2...@gmail.com
FYI we are archiving compressed Linux disk images for VMs and
hypervisors.
A core problem is that you've got the worst sort of data for something
like Git. Your files are huge, and being compressed, any effort to
compress saved files or find duplicate
From: Alain raf.n...@gmail.com
but what i do not understand is if only 1 person manage the bare repository
(setting access right to this repository) on local disk, how can he prevent
other people to modify, stage and push changes to it ?
Moreover, the bare repository is not for only 1
On Fri, 16 May 2014 10:43:20 -0400
wor...@alum.mit.edu (Dale R. Worley) wrote:
Sorry to replying to your message, not OP's.
FYI we are archiving compressed Linux disk images for VMs and
hypervisors.
A core problem is that you've got the worst sort of data for something
like Git. Your
On Fri, 16 May 2014 19:53:35 +0400
Konstantin Khomoutov flatw...@users.sourceforge.net wrote:
[...]
Another approach is to use a backup tool which performs block-level
deduplication. For this, I can name obnam [3] and ZFS (snapshotting
with block-level dedup turned on).
Attic [1] does
On Friday, May 16, 2014 10:45:10 AM UTC+2, Thomas Ferris Nicolaisen wrote:
On Friday, May 16, 2014 8:22:30 AM UTC+2, Andy wrote:
For a 'release' we'd send the customer a complete set of files, but
often a fix only requires one or two files to be modified which we ask
the customer to
On 05/16/2014 03:13 AM, Duy Nguyen wrote:
On Fri, May 16, 2014 at 2:06 AM, Philip Oakley philipoak...@iee.org wrote:
From: John Fisher fishook2...@gmail.com
I assert based on one piece of evidence ( a post from a facebook dev) that
I now have the worlds biggest and slowest git
repository,
12 matches
Mail list logo
