From mboxrd@z Thu Jan 1 00:00:00 1970 From: Torsten Wagner Subject: Re: using org mode and git efficiently Date: Thu, 3 Jan 2013 16:20:22 +0100 Message-ID: References: <87bod6xtqx.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d042e02e5d206d604d263e6b9 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:58999) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tqmlm-00050V-3a for emacs-orgmode@gnu.org; Thu, 03 Jan 2013 10:31:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tqmam-0005WY-IC for emacs-orgmode@gnu.org; Thu, 03 Jan 2013 10:20:41 -0500 Received: from mail-pa0-f50.google.com ([209.85.220.50]:59415) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tqmam-0005VO-3f for emacs-orgmode@gnu.org; Thu, 03 Jan 2013 10:20:24 -0500 Received: by mail-pa0-f50.google.com with SMTP id hz10so8705172pad.9 for ; Thu, 03 Jan 2013 07:20:23 -0800 (PST) In-Reply-To: <87bod6xtqx.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Luca Ferrari Cc: emacs-orgmode@gnu.org --f46d042e02e5d206d604d263e6b9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 =A8before=A8 and =A8after=A8 lin= ks. I believe that this is a very important feature if you work with git and or= g Greetings Torsten On 3 January 2013 14:48, Jambunathan K wrote: > Luca Ferrari 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 > > > > > > -- > > --f46d042e02e5d206d604d263e6b9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

there exist a contrib=A0
which allows you to link to speci= fic versions of a file under git control.
Thus, you can describe a error/feature/behavior=A0in a file and make s= ure the description remains valid even if you change the file in the mean t= ime.
E.g. you can document your bug fixing with =A8before=A8 and = =A8after=A8 links.
=A0
I believe that this is a very important feature if you w= ork with git and org

Greetings

Torsten


On 3 January 201= 3 14:48, Jambunathan K <kjambunathan@gmail.com> wrote:<= br>
Luca= Ferrari <fluca1978@infinito.it= > writes:

> Hi all,
> I'm using Org mode to manage my coding projects, that are all base= d 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
=A0 =A0 =A0 =A0 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
=A0 =A0 =A0 =A0 C-x 4 a

can identify the function where the change was made. =A0I don't whether= in
Org-mode the nearest headline (which qualifies as 'nearest function'= ;)
gets picked up. =A0If not, you can make a feature request.

See also
=A0 =A0 =A0 =A0 (info "(org) Attachments")

> Thanks,
> Luca
>
>

--


--f46d042e02e5d206d604d263e6b9--