On Jun 2, 2010, at 9:44 AM, Christian Egli wrote:
Hi Carsten
Carsten Dominik writes:
are we ready to install org-taskjuggler.el into Org-mode?
I modified it so that it no longer uses the ID property, so from that
perspective it should be ready. What is missing is a little section
for
th
Hi Carsten
Carsten Dominik writes:
> are we ready to install org-taskjuggler.el into Org-mode?
I modified it so that it no longer uses the ID property, so from that
perspective it should be ready. What is missing is a little section for
the manual and the integration in the the exporter and the
Hi Christian,
are we ready to install org-taskjuggler.el into Org-mode?
Where do you want it, core or contrib?
I did not yet hear from you that the FSF assignment process
is done, could you please update me on that?
Thanks.
- Carsten
On May 21, 2010, at 11:10 PM, Christian Egli wrote:
Hi al
On Fri, May 21 2010, Christian Egli wrote:
> So before pouring out the baby with the bathwater maybe we should at
> least try if the git merge driver solves the main problem we have with
> the Changelog files.
This does not resolve a ugly part which is the duplication of
information: in the cha
Hi all
John Wiegley writes:
> The Emacs ChangeLog is a file which predates the existence of freely
> available, project-wide version control. It was a way to see, in one
> place, the stream of changes occurring in a project -- something which
> RCS could not do for you.
The only problem is that
Bernt Hansen writes:
> John Wiegley writes:
>
>> On May 21, 2010, at 9:47 AM, Tassilo Horn wrote:
>>
>>> I think it would be better if line 3+ would be exact ChangeLog entries
>>> format-wise, so that you can still use emacs' ChangeLog facilities
>>> (`add-change-log-entry'). I don't really wan
On May 21, 2010, at 11:53 AM, Carsten Dominik wrote:
> But only the file, not the function...
I tested it with a function change, and it inserted the function name too!
John
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the
On May 21, 2010, at 11:39 AM, Bernt Hansen wrote:
> I make most of my git commits (including org-mode) in vim which is
> kicked off from raw command-line git. I normally make multiple changes
> at once and then build separate commits by using git's editing hunk
> features from 'git add -p'. I do
John Wiegley writes:
> On May 21, 2010, at 11:39 AM, Bernt Hansen wrote:
>
>> I make most of my git commits (including org-mode) in vim which is
>> kicked off from raw command-line git. I normally make multiple changes
>> at once and then build separate commits by using git's editing hunk
>> fea
John Wiegley writes:
> On May 21, 2010, at 9:47 AM, Tassilo Horn wrote:
>
>> I think it would be better if line 3+ would be exact ChangeLog entries
>> format-wise, so that you can still use emacs' ChangeLog facilities
>> (`add-change-log-entry'). I don't really want to write the changed file
>>
So, I suppose starting now we can just stop updating the ChangeLog.
Here is an example of how a properly formatted entry would become a commit
message:
2010-05-19 David Maus
* org.el (org-refile-cache-get): Return empty list of targets
when cache was cleared.
(org-clo
On May 21, 2010, at 5:06 PM, John Wiegley wrote:
On May 21, 2010, at 9:47 AM, Tassilo Horn wrote:
I think it would be better if line 3+ would be exact ChangeLog
entries
format-wise, so that you can still use emacs' ChangeLog facilities
(`add-change-log-entry'). I don't really want to write
On May 21, 2010, at 10:32 AM, Carsten Dominik wrote:
> We could even make a command for this, and apply any wanted
> formatting like what John was proposing (removing the committer
> line and indentation)...
>
> I think that this is not a bad idea, because normally you will
> not have the commit
On May 21, 2010, at 9:47 AM, Tassilo Horn wrote:
> I think it would be better if line 3+ would be exact ChangeLog entries
> format-wise, so that you can still use emacs' ChangeLog facilities
> (`add-change-log-entry'). I don't really want to write the changed file
> and function names on my own,
On May 21, 2010, at 2:50 PM, John Wiegley wrote:
On May 21, 2010, at 8:15 AM, Carsten Dominik wrote:
Can I have a look at one of those ChangeLog files created with the
script? Just to get the idea? Do we need to do something special
in the git commit message?
Below is output from runni
Hi Ben,
On May 21, 2010, at 3:01 PM, Ben Finney wrote:
Carsten Dominik writes:
On May 21, 2010, at 11:41 AM, John Wiegley wrote:
This makes it trivial to build ChangeLog entries for a range of
commits, suitable for submission to Emacs. It may need a bit more
work to be production-ready, but
John Wiegley writes:
Hi John,
> Line 1 is a <50 character short description
>
> Line 3 starts a 72-column full commit entry, formatted just like a
> ChangeLog entry, but without leading whitespace or '*'. If a changed
> file is mentioned, the mention isn't repeated by git-changelog; but
Carsten Dominik writes:
> On May 21, 2010, at 11:41 AM, John Wiegley wrote:
> > This makes it trivial to build ChangeLog entries for a range of
> > commits, suitable for submission to Emacs. It may need a bit more
> > work to be production-ready, but it can already produce a ChangeLog
> > for all
On May 21, 2010, at 8:15 AM, Carsten Dominik wrote:
> Can I have a look at one of those ChangeLog files created with the script?
> Just to get the idea? Do we need to do something special in the git commit
> message?
Below is output from running "git changelog HEAD~15.. -- lisp". It can
ide
On May 21, 2010, at 11:41 AM, John Wiegley wrote:
I just remembered that I'd written a script for building a properly
formatted ChangeLog directly from Git history:
http://github.com/jwiegley/git-scripts/blob/master/git-changelog
This makes it trivial to build ChangeLog entries for a ran
I just remembered that I'd written a script for building a properly formatted
ChangeLog directly from Git history:
http://github.com/jwiegley/git-scripts/blob/master/git-changelog
This makes it trivial to build ChangeLog entries for a range of commits,
suitable for submission to Emacs. It
21 matches
Mail list logo
