From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Re: Internal links in LaTeX export
Date: Sat, 30 Oct 2010 12:56:20 -0700 [thread overview]
Message-ID: <AANLkTi=eAw2=a9ZbyjMGfj=pbTghab+aCLtyR90MkjZO@mail.gmail.com> (raw)
In-Reply-To: <81fwvpnw0n.fsf@gmail.com>
Hi Jambunathan
On 29 October 2010 03:17, Jambunathan K <kjambunathan@gmail.com> wrote:
> wish there was a way to say this:
>
> - "do bisection on the revisions where org-latex.el changed (as opposed
> to revisions where HEAD moved)"
>
> The candidate commits then would have reduced to 30 odd commits rather
> than 851 that one had to contend with.
>
I see in `man git-bisect' a form like this is shown as valid,
git bisect start [<bad> [<good>...]] [--] [<paths>...]
Wouldn't that do the job?
PS: I haven't tried this, just referring to the docs.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2010-10-30 19:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 20:06 Internal links in LaTeX export Thomas S. Dye
2010-10-28 20:18 ` Sébastien Vauban
2010-10-28 20:44 ` Thomas S. Dye
2010-10-28 21:01 ` Jambunathan K
2010-10-28 21:19 ` Thomas S. Dye
2010-10-28 22:35 ` Nick Dokos
2010-10-29 0:20 ` Thomas S. Dye
2010-10-29 1:30 ` Jambunathan K
2010-10-29 2:04 ` Thomas S. Dye
2010-10-29 3:22 ` [SOLVED] " Jambunathan K
2010-10-29 3:58 ` Carsten Dominik
2010-10-29 5:01 ` Noorul Islam K M
2010-10-29 6:38 ` Tom Dye
2010-10-29 7:20 ` Nick Dokos
2010-10-29 7:51 ` Noorul Islam
2010-10-29 8:34 ` Nick Dokos
2010-11-13 5:55 ` [Accepted] " Carsten Dominik
2010-10-29 3:28 ` Nick Dokos
2010-10-29 5:46 ` Nick Dokos
2010-10-29 10:17 ` Jambunathan K
2010-10-30 19:56 ` suvayu ali [this message]
2010-11-02 7:35 ` Jambunathan K
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='AANLkTi=eAw2=a9ZbyjMGfj=pbTghab+aCLtyR90MkjZO@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=nicholas.dokos@hp.com \
/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).