From: Torsten Wagner <torsten.wagner@gmail.com>
To: Luca Ferrari <fluca1978@infinito.it>
Cc: emacs-orgmode@gnu.org
Subject: Re: using org mode and git efficiently
Date: Thu, 3 Jan 2013 16:20:22 +0100 [thread overview]
Message-ID: <CAPaq-gNqyMWV6Cp5kovMODjz1sJTV4FHqb_zyBGUa6PKb6-LrA@mail.gmail.com> (raw)
In-Reply-To: <87bod6xtqx.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
Hi,
there exist a contrib
http://orgmode.org/worg/org-contrib/org-git-link.html
which allows you to link to specific versions of a file under git control.
Thus, you can describe a error/feature/behavior in a file and make sure the
description remains valid even if you change the file in the mean time.
E.g. you can document your bug fixing with ¨before¨ and ¨after¨ links.
I believe that this is a very important feature if you work with git and org
Greetings
Torsten
On 3 January 2013 14:48, Jambunathan K <kjambunathan@gmail.com> wrote:
> Luca Ferrari <fluca1978@infinito.it> writes:
>
> > Hi all,
> > I'm using Org mode to manage my coding projects, that are all based on
> > git. I was wondering if there are tips and tricks to use the two
> > efficiently, for instance storing the current head when a task is
> > marched as completed in org mode, so that the task can "link" to the
> > commit that completed a feature. Also having the commit text being
> > based on the org task one (or viceversa?) could be useful.
> > Anyone has an hint on how to achieve a more org-to-git integration?
> > I'm using magit to what it matters.
>
> Try
> C-x v g and/or C-x v l
>
> in your version controlled Org file.
>
> In conventional prog-modes, while preparing a ChangeLog entry
> C-x 4 a
>
> can identify the function where the change was made. I don't whether in
> Org-mode the nearest headline (which qualifies as 'nearest function')
> gets picked up. If not, you can make a feature request.
>
> See also
> (info "(org) Attachments")
>
> > Thanks,
> > Luca
> >
> >
>
> --
>
>
[-- Attachment #2: Type: text/html, Size: 2418 bytes --]
next prev parent reply other threads:[~2013-01-03 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 13:20 using org mode and git efficiently Luca Ferrari
2013-01-03 13:48 ` Jambunathan K
2013-01-03 15:20 ` Torsten Wagner [this message]
2013-01-03 15:26 ` Luca Ferrari
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPaq-gNqyMWV6Cp5kovMODjz1sJTV4FHqb_zyBGUa6PKb6-LrA@mail.gmail.com \
--to=torsten.wagner@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fluca1978@infinito.it \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).