linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs-1.39-tyt3
Date: Tue, 1 May 2007 12:49:56 -0600	[thread overview]
Message-ID: <20070501184956.GF5722@schatzie.adilger.int> (raw)
In-Reply-To: <20070501150545.GA26093@thunk.org>

On May 01, 2007  11:05 -0400, Theodore Tso wrote:
> Speaking of SCM's, how wedded is Clustrefs to mercurial?  I've been
> considering migrating e2fsprogs development to git, but one of the
> reasons I haven't is because I was concerned that might be incovenient
> for you folks.

Not at all, we just generate a 1.39 to 1.39-WIP patch, and then use
quilt + CVS to manage the resulting patches.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

      reply	other threads:[~2007-05-01 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 15:22 e2fsprogs-1.39-tyt3 Theodore Ts'o
2007-05-01  7:56 ` e2fsprogs-1.39-tyt3 Andreas Dilger
2007-05-01 15:05   ` e2fsprogs-1.39-tyt3 Theodore Tso
2007-05-01 18:49     ` Andreas Dilger [this message]

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=20070501184956.GF5722@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).