On Thu, 3 Jan 2019 00:25:29 +0100
Jonas Stein wrote:
> git log | grep "Author: "| sort | uniq | sed "s/Author: //g" | wc -c
That's a rather round about way of doing :
git shortlog -e -s | cut -f 2
git shortlog -e -s | cut -f 2 | wc -c
37471
git shortlog -e -s | wc -l
998
>> Are there any long-lived community FOSS projects maintaining such
>> file?
>
> GNU Emacs:
> http://git.savannah.gnu.org/cgit/emacs.git/tree/etc/AUTHORS
> They add everyone who has contributed, and after 33 years the file
> has grown to 170 kB, which I think is still acceptable. We have some
>
On Tue, Nov 27, 2018 at 01:50:31PM -0800, Matt Turner wrote:
> So let's satisfy everyone and be done with it: Let's put AUTHORS in
> Git with a section header that states that these Copyright holders are
> not obvious from the git history. This is where Sony would go.
We can make it obvious from
On Tue, Nov 27, 2018 at 5:49 PM Michał Górny wrote:
>
> On Tue, 2018-11-27 at 16:01 -0500, Rich Freeman wrote:
> > On Tue, Nov 27, 2018 at 3:42 PM Kent Fredric wrote:
> > >
> > > That git manages not to die every day based on what we throw at it is
> > > frankly a miracle of engineering.
> >
> >
On Tue, 2018-11-27 at 16:01 -0500, Rich Freeman wrote:
> On Tue, Nov 27, 2018 at 3:42 PM Kent Fredric wrote:
> >
> > That git manages not to die every day based on what we throw at it is
> > frankly a miracle of engineering.
>
> Our repo is a linked list being constantly manipulated from the
On Tue, Nov 27, 2018 at 4:50 PM Matt Turner wrote:
>
> Or, I don't know. Come up with something better and continue
> bikeshedding. I won't.
>
I think antarus already came up with something better - let Sony
explain its thinking, rather than trying to guess at what they're
trying to accomplish
On Tue, Nov 27, 2018 at 12:11 PM Rich Freeman wrote:
>
> On Tue, Nov 27, 2018 at 2:58 PM Matt Turner wrote:
> >
> > What Copyright-owner header are you talking about?
>
> We would create one, just as we've created bugzilla tags in git for
> closing bugs/etc. Surely putting one line in a commit
On Wed, 28 Nov 2018 10:11:32 +1300
Kent Fredric wrote:
> Just don't try using filter branch on a whole gentoo repository, you'll
> quickly learn why. ( You'll find yourself having to employ lots of
> tricks with git fast-export instead just to avoid projected times in
> weeks )
Hah. Fun fact.
On Tue, 27 Nov 2018 16:01:15 -0500
Rich Freeman wrote:
> Our repo is a linked list being constantly manipulated from the head
> backed by a hashed object store for the contents. For that use case
> it is probably the ideal data structure. Since our use case is
> actually the typical use case,
On Tue, Nov 27, 2018 at 3:42 PM Kent Fredric wrote:
>
> That git manages not to die every day based on what we throw at it is
> frankly a miracle of engineering.
Our repo is a linked list being constantly manipulated from the head
backed by a hashed object store for the contents. For that use
On Tue, 27 Nov 2018 12:51:00 -0500
Rich Freeman wrote:
> As others have pointed out, it seems like other projects are moving
> away from AUTHORS files in favor of git.
"Other projects" don't typically have repos so large that a simple
application of a git filter-branch could take weeks.
That
On Tue, Nov 27, 2018 at 3:34 PM Michał Górny wrote:
>
> Please don't forget we're talking about Gentoo, so brace for 2 weeks of
> bikeshedding over whether first or last name should come first.
>
Thank goodness there isn't a Mike Gordon on the rolls or we could
discuss the intricacies of UTF-8
On Tue, 27 Nov 2018 15:10:36 -0500
Rich Freeman wrote:
> Also, GLEP 76 as it is written says: "Projects using this scheme must
> track authorship in a VCS, unless they list all authors of
> copyrightable contributions in an AUTHORS file."
Idea: How about using VCS as a defacto set of AUTHORS,
On Tue, 2018-11-27 at 15:29 -0500, Craig Andrews wrote:
> On 27.11.2018 15:23, William Hubbs wrote:
> > On Tue, Nov 27, 2018 at 09:15:08PM +0100, Michał Górny wrote:
> > > On Tue, 2018-11-27 at 14:07 -0600, William Hubbs wrote:
> > > > All,
> > > > I just picked a random msg to reply to on the
On Tue, Nov 27, 2018 at 3:23 PM William Hubbs wrote:
>
> On Tue, Nov 27, 2018 at 09:15:08PM +0100, Michał Górny wrote:
> > On Tue, 2018-11-27 at 14:07 -0600, William Hubbs wrote:
> > > All,
> > > I just picked a random msg to reply to on the thread.
> > >
> > > Here is the updated AUTHORS file I
On 27.11.2018 15:23, William Hubbs wrote:
On Tue, Nov 27, 2018 at 09:15:08PM +0100, Michał Górny wrote:
On Tue, 2018-11-27 at 14:07 -0600, William Hubbs wrote:
> All,
> I just picked a random msg to reply to on the thread.
>
> Here is the updated AUTHORS file I would like to commit.
>
You
On Tue, Nov 27, 2018 at 3:15 PM Michał Górny wrote:
>
> On Tue, 2018-11-27 at 14:07 -0600, William Hubbs wrote:
> > All,
> > I just picked a random msg to reply to on the thread.
> >
> > Here is the updated AUTHORS file I would like to commit.
> >
>
> You should include at least all current
On Tue, Nov 27, 2018 at 09:15:08PM +0100, Michał Górny wrote:
> On Tue, 2018-11-27 at 14:07 -0600, William Hubbs wrote:
> > All,
> > I just picked a random msg to reply to on the thread.
> >
> > Here is the updated AUTHORS file I would like to commit.
> >
>
> You should include at least all
On Tue, 2018-11-27 at 14:07 -0600, William Hubbs wrote:
> All,
> I just picked a random msg to reply to on the thread.
>
> Here is the updated AUTHORS file I would like to commit.
>
You should include at least all current developers with commit access.
Because otherwise, this really looks like
On Tue, Nov 27, 2018 at 2:58 PM Matt Turner wrote:
>
> What Copyright-owner header are you talking about?
We would create one, just as we've created bugzilla tags in git for
closing bugs/etc. Surely putting one line in a commit is no more
difficult than putting one file in a repository? Indeed
On 11/27/18 9:07 PM, William Hubbs wrote:
> All,
> I just picked a random msg to reply to on the thread.
>
> Here is the updated AUTHORS file I would like to commit.
>
> William
Lets put it on agenda for next council meeting and let the discussion go
until then.
--
Kristian Fiskerstrand
All,
I just picked a random msg to reply to on the thread.
Here is the updated AUTHORS file I would like to commit.
William
# This is the official list of Gentoo package authors for copyright purposes.
# This file is maintained manually.
# To be included, send a change adding the individual or
On Tue, Nov 27, 2018 at 9:49 AM Rich Freeman wrote:
>
> On Tue, Nov 27, 2018 at 11:59 AM Matt Turner wrote:
> >
> > On Tue, Nov 27, 2018 at 7:41 AM Rich Freeman wrote:
> > > It makes sense to ensure that the solution actually solves the problem
> > > before we simply implement it.
> > >
> > >
On Tue, Nov 27, 2018 at 12:49 PM Rich Freeman wrote:
>
> On Tue, Nov 27, 2018 at 11:59 AM Matt Turner wrote:
> >
> > On Tue, Nov 27, 2018 at 7:41 AM Rich Freeman wrote:
> > > It makes sense to ensure that the solution actually solves the problem
> > > before we simply implement it.
> > >
> > >
On Tue, Nov 27, 2018 at 12:31 PM William Hubbs wrote:
>
> Agreed, we should not add every developer to this file by default.
>
Isn't this basically giving the most credit to the most
difficult-to-work-with entities by default?
As others have pointed out, it seems like other projects are moving
On Tue, Nov 27, 2018 at 11:59 AM Matt Turner wrote:
>
> On Tue, Nov 27, 2018 at 7:41 AM Rich Freeman wrote:
> > It makes sense to ensure that the solution actually solves the problem
> > before we simply implement it.
> >
> > If we really need such a file it would probably also make more sense
>
On Tue, Nov 27, 2018 at 06:01:58PM +0100, Ulrich Mueller wrote:
> > On Tue, 27 Nov 2018, Andrey Utkin wrote:
>
> > It seems to me this will grow huge, and be the source of annoyance for
> > users.
>
> IIUC the file has a specific purpose, namely to solve the copyright
> attribution problem.
On Tue, Nov 27, 2018 at 10:40:57AM -0500, Rich Freeman wrote:
> On Tue, Nov 27, 2018 at 10:16 AM Michał Górny wrote:
> >
> > Will that actually solve any problem, or just add another half-baked
> > solution with no benefit to the resulting status? In other words, would
> > SIE suddenly stop
> On Tue, 27 Nov 2018, Andrey Utkin wrote:
> It seems to me this will grow huge, and be the source of annoyance for
> users.
IIUC the file has a specific purpose, namely to solve the copyright
attribution problem. So only those entities who would otherwise add
themselves to ebuild headers
On Tue, Nov 27, 2018 at 7:58 AM Andrey Utkin wrote:
>
> On Tue, Nov 27, 2018 at 09:12:26AM -0600, William Hubbs wrote:
> > All,
> >
> > based on the previous thread about copyright attribution clarifications,
> > I want to add the following AUTHORS file to the top level of the portage
> >
On Tue, Nov 27, 2018 at 7:41 AM Rich Freeman wrote:
> It makes sense to ensure that the solution actually solves the problem
> before we simply implement it.
>
> If we really need such a file it would probably also make more sense
> to have it auto-generated from git commit headers
And how do
On Tue, Nov 27, 2018 at 09:12:26AM -0600, William Hubbs wrote:
> All,
>
> based on the previous thread about copyright attribution clarifications,
> I want to add the following AUTHORS file to the top level of the portage
> repository if no one objects.
>
> This is based on the description of
On Tue, Nov 27, 2018 at 10:16 AM Michał Górny wrote:
>
> Will that actually solve any problem, or just add another half-baked
> solution with no benefit to the resulting status? In other words, would
> SIE suddenly stop requiring you to alter copyright in ebuilds?
++
It makes sense to ensure
On Tue, 2018-11-27 at 09:12 -0600, William Hubbs wrote:
> All,
>
> based on the previous thread about copyright attribution clarifications,
> I want to add the following AUTHORS file to the top level of the portage
> repository if no one objects.
>
> This is based on the description of the
34 matches
Mail list logo
