-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/30/2013 07:37 PM, Michał Górny wrote:
> Hello, all.
>
> After a few days of thinking, discovering and working, here it is.
> The first working draft of new git eclass codenamed 'git-r3'.
>
> First of all, the name is not final. I'm open to idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The new eclass is supposedly used by 732 in-tree packages [1],
> and possibly a few dozens out-of-the-tree. Some parts of the eclass API
> are barely used. I would really prefer to avoid yet another eclass
> migration.
that's a shame, I don't think
On 31 August 2013 00:37, Michał Górny wrote:
> Hello, all.
>
> After a few days of thinking, discovering and working, here it is.
> The first working draft of new git eclass codenamed 'git-r3'.
>
> First of all, the name is not final. I'm open to ideas. I'm open to
> naming it 'git-r1' to put it i
Do you have any plans to add support for sparse checkout?
Something like this
|cd
git clone -n
cd
git remote add –f
git config core.sparsecheckout true
echo // >> .git/info/sparse-checkout
git checkout
(Credit goes to :
http://stackoverflow.com/questions/15827117/git-sparse-checkout-for-
On 08/28/2013 10:00 AM, Michał Górny wrote:
>
> What are your thoughts?
>
Not interested in any of those suggestions. git-2.eclass works fine for
me and I will keep using it.
Hello, all.
After a few days of thinking, discovering and working, here it is.
The first working draft of new git eclass codenamed 'git-r3'.
First of all, the name is not final. I'm open to ideas. I'm open to
naming it 'git-r1' to put it in line with my other -r1 eclasses :).
I'd definitely like
On Tue, 2013-08-20 at 16:12 -0400, Michael Orlitzky wrote:
> > # Redmine
> > =dev-ruby/builder-3.1.4 ~amd64
> > =dev-ruby/rails-3.2.13 ~amd64
> Ok, this one is ridiculous. The stable version of Rails is 2.3.18, and
> 3.0 was released almost exactly three years ago. Every time rails-3.x
> gets bum