From: "Rick Moynihan" <rick.moynihan@gmail.com>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: custom link type for files in a git repo
Date: Tue, 7 Oct 2008 03:01:30 +0100 [thread overview]
Message-ID: <e85471e30810061901o5d1b3bdq69c8e4ca5fef77c@mail.gmail.com> (raw)
In-Reply-To: <m0wsgme3sw.fsf@gmail.com>
2008/10/6 Austin Frank <austin.frank@gmail.com>:
--- snip ---
>
> Now that org and git are starting to be used in conjunction by more and
> more of us, would anyone else find it useful to have a custom link type
> for linking to git objects?
Absolutely!! git is my new favourite tool, and being able to combine
org-mode and git in a usable workflow would be a great idea!
> I could imagine that calling org-store-link on a file or directory that
> is in a git repo could link to the current HEAD version, and we could
> have access to all of the information from calling git-log on the file
> (commit, author, date, message). Similarly, we'd want to be able to
> link to arbitrary objects in the repo's history (tags, particular
> commits, merge points, etc).
This sounds like it'd be handy, as I've already found myself pasting
git SHA's into org-mode! So having these (plus a path to a local
repo) link to the specific commits would be awesome. More than this
though I want integration with git commit messages!
> I think most of this could be done via git.el that is distributed with
> git. One cool application of this would be a git post-commit-hook that
> called remember to create a link to the new commit in the relevant
> project file.
Yeah, this sounds like exactly what I'd want! :-) Ideally it'd also
be branch aware. And I can imagine that having each commit as an
outline with a tag of the branch name and a property drawer containing
the SHA (as a link) would be enough for a start!
It'd make sense to follow the git tradition of having the first line
of the commit message default to the outline's title in org.
> This would be a really neat way to keep a timeline for a
> particular project's commits right alongside all of the other
> information stored in org. I can also see it being really useful to
> link to a particular version of a non-org file within some org notes.
> That file might change, making it difficult to interpret some notes or
> making specific line numbers irrelevant, but a link to the exact version
> being discussed would make such notes future proof.
This would probably be quite handy too, though I think getting commits
into the agenda would be better :-)
> I think I could probably get at least a skeleton of these kinds of
> functions working myself, but I won't be able to get to it until the
> winter holidays. If these ideas scratch the itches of another org user
> who wants to code this up, I promise I'll a) use it b) praise your
> awesomeness, and c) buy you a beer if we're ever in the same city.
>
> Thoughts? Other features that could go into this?
>
> Thanks,
> /au
>
>
> --
> Austin Frank
> http://aufrank.net
> GPG Public Key (D7398C2F): http://aufrank.net/personal.asc
R.
next prev parent reply other threads:[~2008-10-07 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 4:38 custom link type for files in a git repo Austin Frank
2008-10-07 2:01 ` Rick Moynihan [this message]
2008-10-07 7:20 ` Ian Barton
2008-10-07 10:55 ` Jason F. McBrayer
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=e85471e30810061901o5d1b3bdq69c8e4ca5fef77c@mail.gmail.com \
--to=rick.moynihan@gmail.com \
--cc=austin.frank@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).