Re: [PATCH 06/11] commit: add tests of commit races

2015-02-11 Thread Junio C Hamano
Michael Haggerty mhag...@alum.mit.edu writes: On the other hand, there's this [1] and this [2] from the FSF, which recommend a copyright blurb at the beginning of every source file. Though actually the recommendation is to include a GPL blurb too, not just a naked copyright line like I used.

Re: [PATCH 06/11] commit: add tests of commit races

2015-02-11 Thread Stefan Beller
On Wed, Feb 11, 2015 at 10:10 AM, Junio C Hamano gits...@pobox.com wrote: Michael Haggerty mhag...@alum.mit.edu writes: On the other hand, there's this [1] and this [2] from the FSF, which recommend a copyright blurb at the beginning of every source file. Though actually the recommendation is

Re: [PATCH 06/11] commit: add tests of commit races

2015-02-11 Thread Junio C Hamano
Stefan Beller sbel...@google.com writes: Quoting from wikipedia[1] (note however that when the United States joined the Convention in 1988, it continued to make statutory damages and attorney's fees only available for registered works). Does that mean if somebody would infringe the GPL on

Re: [PATCH 06/11] commit: add tests of commit races

2015-02-11 Thread Michael Haggerty
On 02/10/2015 08:12 PM, Junio C Hamano wrote: Stefan Beller sbel...@google.com writes: On Sun, Feb 8, 2015 at 8:14 AM, Michael Haggerty mhag...@alum.mit.edu wrote: +# Copyright (c) 2014 Michael Haggerty mhag...@alum.mit.edu What is the projects stance on copyright lines? I do not

Re: [PATCH 06/11] commit: add tests of commit races

2015-02-10 Thread Junio C Hamano
Stefan Beller sbel...@google.com writes: On Sun, Feb 8, 2015 at 8:14 AM, Michael Haggerty mhag...@alum.mit.edu wrote: +# Copyright (c) 2014 Michael Haggerty mhag...@alum.mit.edu What is the projects stance on copyright lines? I do not think we have a strong one. I've seen files (most of

Re: [PATCH 06/11] commit: add tests of commit races

2015-02-09 Thread Stefan Beller
On Sun, Feb 8, 2015 at 8:14 AM, Michael Haggerty mhag...@alum.mit.edu wrote: diff --git a/t/t7516-commit-races.sh b/t/t7516-commit-races.sh new file mode 100755 index 000..5efa351 --- /dev/null +++ b/t/t7516-commit-races.sh @@ -0,0 +1,38 @@ +#!/bin/sh +# +# Copyright (c) 2014 Michael

[PATCH 06/11] commit: add tests of commit races

2015-02-08 Thread Michael Haggerty
Committing involves the following steps: 1. Determine the current value of HEAD (if any). 2. Create the new commit object. 3. Update HEAD. Please note that step 2 can take arbitrarily long, because it might involve the user editing a commit message. If a second process sneaks in a commit during