public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brandon Philips <brandon@ifup.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: merging acl-dev and attr-dev [was: Re: [patch 0/4] attr: test/ improvements and integrate with make]
Date: Mon, 9 Feb 2009 11:09:50 -0800	[thread overview]
Message-ID: <20090209190950.GF21254@jenkins.ifup.org> (raw)
In-Reply-To: <20090209181257.GA18112@infradead.org>

On 13:12 Mon 09 Feb 2009, Christoph Hellwig wrote:
> On Sun, Feb 08, 2009 at 11:59:59PM +0100, Andreas Gruenbacher wrote:
> > >
> > >   http://ifup.org/git/?p=acl-attr-dev.git;a=summary
> > >   git clone git://ifup.org/philips/acl-attr-dev.git
> > >
> > > What do you think?
> > 
> > I believe it's a good start; we probably want to merge the trees eventually. 
> > The way how you have moved libmisc breaks the tarballs though; I have fixed 
> > it. Also, I was surprised that your repository has all the history rewritten 
> > instead of merging Christoph's trees, so I redid the merge.
> 
> I think the merge is a bad idea.  attr and acl serve quite
> different purposes and have been different source and binary packages in
> distros forever. 

They can remain different binary packages after merging the source code
repos to share libmisc.

> I'd rather keep it as it was for now and maybe find
> some way libacl could pick up libmisc from libattr.
>
> There's a reason we split up xfs-cmds into more manageable
> repositories.

What was the reason for splitting these two packages from each other?

>From looking at the shortlogs it looks like a lot of the bug fixes are
made against attr then copied over to acl: 

 http://ifup.org/git/?p=acl-attr-dev.git;a=shortlog

> I'd rather keep it as it was for now and maybe find
> some way libacl could pick up libmisc from libattr.

Perhaps. Although, it doesn't seem right making walk_tree or the quoting
code available to applications through libacl.

Cheers,

	Brandon

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-02-09 19:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  2:19 [patch 0/4] attr: test/ improvements and integrate with make brandon
2009-01-08  2:19 ` [patch 1/4] [PATCH] attr: move ext2/3 tests into seperate test file brandon
2009-01-08  2:19 ` [patch 2/4] [PATCH] attr: various improvements for test/run brandon
2009-01-08  2:19 ` [patch 3/4] [PATCH] attr: add make test target and use make to run tests brandon
2009-01-08  2:19 ` [patch 4/4] [PATCH] attr: Tests for path recursion with -L -P -R brandon
2009-01-08 15:44 ` [patch 0/4] attr: test/ improvements and integrate with make Christoph Hellwig
2009-01-08 16:58   ` Brandon Philips
2009-02-07  9:10     ` Brandon Philips
2009-02-08 22:59       ` Andreas Gruenbacher
2009-02-08 23:38         ` Brandon Philips
2009-02-09  0:31           ` Andreas Gruenbacher
2009-02-09 18:12         ` Christoph Hellwig
2009-02-09 19:06           ` Andreas Gruenbacher
2009-02-09 19:09           ` Brandon Philips [this message]
2009-02-10  7:57             ` merging acl-dev and attr-dev [was: Re: [patch 0/4] attr: test/ improvements and integrate with make] Christoph Hellwig

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=20090209190950.GF21254@jenkins.ifup.org \
    --to=brandon@ifup.org \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox