Hi Daimrod,
Daimrod writes:
> Ok, I've already sent an assignment request for another patch and it
> should be confirmed by the end of the week.
Don't be too optimistic, it takes usually longer, at least three
weeks. You can still send patches, we will apply them when the FSF
confirmed your a
Achim Gratz writes:
> Nick Dokos writes:
>> I believe that just as with code changes, doc changes also need FSF
>> copyright assignment.
>
> The FSF owns the copyright to all of Org, including the
> documentation.
More precisely, the FSF owns the copyright of GNU Emacs, and
assignments are sign
Nick Dokos writes:
> Daimrod wrote:
>
>> John Hendy writes:
>>
>> > On Mon, Jan 21, 2013 at 12:41 PM, Daimrod wrote:
>> >> Hi,
>> >>
>> >> It would be nice if the documentation mentioned the need to reparse the
>> >> org buffer with `C-c C-c' when a property is set with #+PROPERTY.
>> >> (inf
Nick Dokos writes:
> I believe that just as with code changes, doc changes also need FSF
> copyright assignment.
The FSF owns the copyright to all of Org, including the documentation.
So yes, anything over 20 lines non-trivial chnages needs to be assigned
to FSF.
Regards,
Achim.
--
+<[Q+ Matri
Daimrod wrote:
> John Hendy writes:
>
> > On Mon, Jan 21, 2013 at 12:41 PM, Daimrod wrote:
> >> Hi,
> >>
> >> It would be nice if the documentation mentioned the need to reparse the
> >> org buffer with `C-c C-c' when a property is set with #+PROPERTY.
> >> (info "(org) Property syntax")
> >
>
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha Daimrod (Greg),
>
> Daimrod writes:
>
>>
>> So, here is a patch for this:
>
> If you add [PATCH] to the email Subject, your patch will be brought to
> the attention of the developers.
I didn't know, thanks.
> All the best,
> Tom
--
Daimrod/Greg
Aloha Daimrod (Greg),
Daimrod writes:
>
> So, here is a patch for this:
If you add [PATCH] to the email Subject, your patch will be brought to
the attention of the developers.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
On Mon, Jan 21, 2013 at 4:35 PM, Daimrod wrote:
> John Hendy writes:
>
>> On Mon, Jan 21, 2013 at 12:41 PM, Daimrod wrote:
>>> Hi,
>>>
>>> It would be nice if the documentation mentioned the need to reparse the
>>> org buffer with `C-c C-c' when a property is set with #+PROPERTY.
>>> (info "(org
Daimrod writes:
> John Hendy writes:
>
>> On Mon, Jan 21, 2013 at 12:41 PM, Daimrod wrote:
>>> Hi,
>>>
>>> It would be nice if the documentation mentioned the need to reparse the
>>> org buffer with `C-c C-c' when a property is set with #+PROPERTY.
>>> (info "(org) Property syntax")
>>
>> As in
John Hendy writes:
> On Mon, Jan 21, 2013 at 12:41 PM, Daimrod wrote:
>> Hi,
>>
>> It would be nice if the documentation mentioned the need to reparse the
>> org buffer with `C-c C-c' when a property is set with #+PROPERTY.
>> (info "(org) Property syntax")
>
> As in adding to the header argumen
On Mon, Jan 21, 2013 at 12:41 PM, Daimrod wrote:
> Hi,
>
> It would be nice if the documentation mentioned the need to reparse the
> org buffer with `C-c C-c' when a property is set with #+PROPERTY.
> (info "(org) Property syntax")
As in adding to the header arguments? Yeah, probably wouldn't hur
Hi,
It would be nice if the documentation mentioned the need to reparse the
org buffer with `C-c C-c' when a property is set with #+PROPERTY.
(info "(org) Property syntax")
And, IMO, it should also be mentioned here:
(info "(org) Buffer-wide header arguments").
A simple footnote like the one pre
12 matches
Mail list logo
