git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: blame -L questions
Date: Mon, 8 Feb 2010 22:03:37 -0500	[thread overview]
Message-ID: <76718491002081903s2e37875bs85eeb55779167ce7@mail.gmail.com> (raw)

Junio,

I'd like git blame to be able to emit multiple blocks when using it
with -L /start/,/end/.

My use case is emitting blocks that are wrapped in

#if defined(WHATEVER)
....
#endif

I was going to use the syntax -L /start/../end/ for this.

I naively thought I might just be able to setup multiple blame_entry's
linked through the next/prev pointers at the start, but that clearly
does not work.

So I was wondering if you could give me any tips about how the
scoreboard, blame_entry, and origin all fit together before I injure
myself. :-)

Thanks,

j.

             reply	other threads:[~2010-02-09  3:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09  3:03 Jay Soffian [this message]
2010-02-09  3:32 ` blame -L questions Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76718491002081903s2e37875bs85eeb55779167ce7@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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. 
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 NNTP newsgroup(s).