mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Aleksey Kuleshov <rndfax@yandex.ru>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] ehci-hcd: remove useless timeout
Date: Sat, 5 Mar 2016 12:15:04 +0300	[thread overview]
Message-ID: <20160305121504.bec4f18e0b3bb403081a87d6@gmail.com> (raw)
In-Reply-To: <6507601457136246@web20j.yandex.ru>

On Sat, 05 Mar 2016 03:04:06 +0300
Aleksey Kuleshov <rndfax@yandex.ru> wrote:

> >>  Was it so necessary?
> >
> > Yes.
> >>  Does Barebox really need this?
> >
> > Yes.
> 
> Oh, these are exhaustive answers, thank you :)
> 
> >>  Or it's just blindly following the rules made by Linux project?
> >
> > It's irrelevant if BB follows this practice blindly, or with extensive
> > knowledge and understanding of all factors involved if the procedure
> > involved is believed to be legally sound
> >
> >>  Do really small projects need to follow all such bureaucratic way rather than
> >>  just growing up?
> >
> > Yes, project with identical licensing, regardless of their size, need
> > to adhere to certain legal procedures in order to have a good case if
> > they are ever in court.
> 
> So this means that every GPL'ed hello-world.c project should follow
> Linux's rules "to have a good case if they are ever in court"?
> 
> And If think in this way then Barebox should create a Barebox Foundation,
> hire a lawyer and wait until someone will sue them. But this is ridiculous, because
> Barebox don't need this! That's why there is no Barebox Foundation with lawyer.
> 
> >>  What if git history magically disappears? Only authors written in files will be fixed,
> >>  but all authors of patches will disappear as well. So this SOB field is only
> >>  valid while "git log" gives you something to read.
> >
> > I don't understand the point you are trying to make.
> 
> SOB is just a matter of "git log".
> 
> >>  But that's for Linux - companies, billions of dollars... What about Barebox?
> > Same license, same rules.
> 
> (see about GPL'ed hello-world.c)
> 
> > Aleksey, I am not really interested in continuing this discussion or
> > trying to convince you to add SOB to your patch, so if any of the
> > above explanations are insufficient for you, I am afraid we are going
> > to have to agree to disagree on this subject.
> 
> I asked a simple question - still no use case of SOB in Barebox.

Of course there is a use case for SOB in Barebox!

Git has the 'Author' placeholder only for one person.
If more that one person works on a patch
then we can't put all their names into the 'Author' field.
However we can use SOB to indicated co-authoring.

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-03-05  8:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 12:48 Aleksey Kuleshov
2016-03-04  7:11 ` Sascha Hauer
2016-03-04 10:42   ` Aleksey Kuleshov
2016-03-04 11:59     ` Antony Pavlov
2016-03-04 12:04       ` Aleksey Kuleshov
2016-03-04 13:59         ` Antony Pavlov
2016-03-04 15:03           ` Aleksey Kuleshov
2016-03-04 17:58         ` Andrey Smirnov
2016-03-04 20:47           ` Aleksey Kuleshov
2016-03-04 22:57             ` Andrey Smirnov
2016-03-05  0:04               ` Aleksey Kuleshov
2016-03-05  9:15                 ` Antony Pavlov [this message]
2016-03-05  9:27                   ` Aleksey Kuleshov

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=20160305121504.bec4f18e0b3bb403081a87d6@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=rndfax@yandex.ru \
    /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