All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Leigh <rleigh@codelibre.net>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Christian MICHON <christian.michon@gmail.com>, git@vger.kernel.org
Subject: Re: git and mtime
Date: Thu, 20 Nov 2008 13:40:55 +0000	[thread overview]
Message-ID: <20081120134055.GB6023@codelibre.net> (raw)
In-Reply-To: <86iqqizgng.fsf@blue.stonehenge.com>

On Thu, Nov 20, 2008 at 05:11:15AM -0800, Randal L. Schwartz wrote:
> >>>>> "Roger" == Roger Leigh <rleigh@codelibre.net> writes:
> 
> Roger> Except in this case I'm storing the content of *tarballs* (along with
> Roger> pristine-tar).  I'm committing exactly what's in the tarball with
> Roger> no changes (this is a requirement).  I can't change the source prior
> Roger> to commit.
> 
> If you're not doing distributed source code development, why are you using
> git?  It's hard to be angry at a screwdriver for not pounding in nails
> properly.

Err, it *is* being used for distributed development... of Debian
packaging.  We track upstream releases on one branch, merge this
periodically onto the master branch containing the Debian packaging
infrastructure, and also have other bits such as a
continually-rebased patches branch to generate quilt patch series
from.  I think you'll find we do actually need to use git.

> Sounds like you want rsync or something.

I think not!  Perhaps if you read my original mail, you might
understand the reasoning behind this (whether you consider that
valid reasoning or not is another matter).


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

  reply	other threads:[~2008-11-20 13:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 11:37 git and mtime Roger Leigh
2008-11-19 12:22 ` Matthias Kestenholz
2008-11-20  8:38   ` Andreas Ericsson
2008-11-20 11:20     ` Roger Leigh
2008-11-20 12:48       ` Andreas Ericsson
2008-11-20 13:12         ` Andreas Ericsson
2008-11-19 12:31 ` Johannes Schindelin
2008-11-19 12:37 ` Arafangion
2008-11-19 14:54   ` Matthieu Moy
2008-11-20  8:39     ` Andreas Ericsson
2008-11-20 10:34     ` Johannes Schindelin
2008-11-20 10:53       ` Matthieu Moy
2008-11-19 13:29 ` Jakub Narebski
2008-11-19 16:18 ` Christian MICHON
2008-11-20 10:35   ` Johannes Schindelin
2008-11-20 11:27   ` Roger Leigh
2008-11-20 13:06     ` Andreas Ericsson
2008-11-20 14:15       ` Roger Leigh
2008-11-20 14:50         ` Andreas Ericsson
2008-11-20 15:19           ` Roger Leigh
2008-11-20 15:33             ` Kyle Moffett
2008-11-20 15:37             ` Andreas Ericsson
2008-11-20 18:36             ` Matthias Kestenholz
2008-11-20 13:11     ` Randal L. Schwartz
2008-11-20 13:40       ` Roger Leigh [this message]
2008-11-20 17:59     ` Daniel Barkalow
2008-11-20 19:24       ` Joey Hess
2008-11-20 13:21 ` martin f krafft
2008-11-20 13:35   ` Roger Leigh
2008-11-20 13:59     ` martin f krafft
2008-11-20 15:56       ` Samuel Tardieu
2008-11-20 14:07     ` Johannes Schindelin
2008-11-20 14:22       ` Roger Leigh

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=20081120134055.GB6023@codelibre.net \
    --to=rleigh@codelibre.net \
    --cc=christian.michon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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.