From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: TIP: using git-bisect
Date: Tue, 03 Jan 2012 15:10:10 -0500 [thread overview]
Message-ID: <87zke48s4d.fsf@newsguy.com> (raw)
In-Reply-To: <8739bxqloe.fsf_-_@dod.no>
Steinar Bang <sb@dod.no> writes:
> Using git bisect applies when a "git pull" leaves you with a broken
> gnus. What I do in that case, is:
[...] snipped the nifty walk thru
Thanks Steiner... that looks really useful
next prev parent reply other threads:[~2012-01-03 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 15:28 nnimap no workee once again Harry Putnam
2012-01-02 16:03 ` Steinar Bang
2012-01-02 22:00 ` Harry Putnam
2012-01-03 7:39 ` TIP: using git-bisect (Was: nnimap no workee once again) Steinar Bang
2012-01-03 20:10 ` Harry Putnam [this message]
2012-01-02 16:27 ` nnimap no workee once again Tassilo Horn
2012-01-07 1:43 ` Ted Zlatanov
2012-01-09 19:13 ` Harry Putnam
2012-01-10 14:50 ` Ted Zlatanov
2012-01-11 3:16 ` Harry Putnam
2012-01-11 3:32 ` Harry Putnam
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=87zke48s4d.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=ding@gnus.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.
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).